SimpleFunctions

Both Teams To Score - 2nd Half · KXWC2HBTTS-26JUN26CPVKSA

Both Teams To Score - 2nd Half is priced at 26¢ midpoint on Kalshi. Current book: 22¢ bid, 30¢ ask, 8¢ spread. This page tracks a standalone prediction-market contract.

Price history

26¢ current

+7¢
10¢20¢30¢
Jun 16, 2026Jun 24, 2026

Contract brief

If Cape Verde and Saudi Arabia both score a goal in the 2nd Half of the Cape Verde vs Saudi Arabia FIFA World Cup match originally scheduled for Jun 26, 2026, then the market resolves to Yes.

Outcome

Both Teams To Score - 2nd Half

Rank

Standalone

Leader

Range

Family volume

$0

Identifier

KXWC2HBTTS-26JUN26CPVKSA-BTTS

Jun 25, 2026, 7:38 AM UTC · 14m ago

Implied probability

26¢
Bid/ask midpoint
Jun 25, 2026, 7:38 AM UTC · 14m ago

Bid

22¢

Ask

30¢

Spread

Reported volume

$0

Family rank

Standalone

Standalone contract

Closes

Jul 11, 2026

Family volume

$0

Orderbook snapshot

22 / 30¢

Kalshi
8¢ spread
BidSize
22¢5
21¢285
20¢625
9¢1.5K
8¢64
AskSize
30¢178
31¢580
50¢1.5K
69¢2.2K
72¢64

Contract terms

What resolves this market.

YES condition

If Cape Verde and Saudi Arabia both score a goal in the 2nd Half of the Cape Verde vs Saudi Arabia FIFA World Cup match originally scheduled for Jun 26, 2026, then the market resolves to Yes.

Venue

Kalshi

Closes

Jul 11, 2026

Identifier

KXWC2HBTTS-26JUN26CPVKSA-BTTS

SF Signal
SF Index
4126.30
Regime
neutral

Event family

KXWC2HBTTS-26JUN26CPVKSA.

The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.

Total volume

$0

Outcomes

1

Highest price

Both Teams To Score - 2nd Half 22¢

Current share

Indicators

Yield, cliff risk, volatility, and regime.

Regime

neutral

Score

0.5

Full indicator table

8252.6%
656.5%
Adj IY
4126%
4

Odds pages

Related prediction questions

Browse odds

Related readings

Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.

Browse library
Technicalguide

Kalshi vs Polymarket: A Developer's Comparison of APIs, Orderbooks, and Liquidity

Data-driven comparison of Kalshi and Polymarket APIs, orderbooks, rate limits, and liquidity. Code examples for building on both prediction markets.

Blogmarkets

Kalshi vs Polymarket: Which Prediction Market Should You Trade?

In-depth comparison of Kalshi and Polymarket for prediction market traders. Regulatory structure, liquidity, fees, API tooling, and cross-venue trading with SimpleFunctions.

Opinioncomparison

Kalshi vs Polymarket: Mechanics, Fees, Regulation, Liquidity (2026)

Side-by-side comparison of Kalshi and Polymarket in 2026. Fee math, calibration data, withdrawal speed, and a decision tree for picking the right venue.

Opinionanalysis

Liquidity Availability Is the Real Edge in Prediction Markets

Implied yield, cliff risk, and overround all describe what to trade. Liquidity Availability Score describes whether the orderbook can absorb the trade. Why LAS is the indicator that decides who actually books P&L.

Technicalguide

Computing Liquidity Availability Score from the Orderbook

Step-by-step guide to computing the Liquidity Availability Score in TypeScript and Python, with edge cases for thin orderbooks, missing data, and the warm-cron coverage limitation.

Blogmarkets

Prediction Market Orderbook Analysis: Reading Depth, Spread, and Liquidity

How to read prediction market orderbooks. Binary settlement, spread-as-percentage, depth asymmetry, executable edge calculation, and cross-venue arbitrage analysis.

SimpleFunctions context

Index, screen, query, and monitor.

Open index

How we compute these odds

SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.

For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.

Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.