SimpleFunctions

All teams collectively score at least 310 goals in the 2026 Men's FIFA World Cup

310+ goals is priced at 39¢ on Kalshi. Current book: 26¢ bid, 39¢ ask, 13¢ spread. This outcome ranks #5 of 7 inside Will all teams collectively score at least.

Price history

39¢ current

+29¢
0¢25¢50¢
May 28, 2026Jun 22, 2026

Contract brief

If all teams collectively record at least 310 goals during the full tournament (including regulation, stoppage, and any extra time periods) of the 2026 Men's FIFA World Cup, then the market resolves to Yes.

Outcome

310+ goals

Rank

#5 of 7

Leader

270+ goals 91¢

Range

12¢-91¢

Family volume

$5K

Identifier

KXWCTOTALGOAL-26FT-310

Jun 22, 2026, 2:38 AM UTC · 12m ago

Implied probability

39¢
Latest venue quote
Jun 22, 2026, 2:38 AM UTC · 12m ago

Bid

26¢

Ask

39¢

Spread

13¢

24h volume

$1K

Family rank

#5 of 7

7 outcomes · Will all teams collectively score at least

Closes

Aug 3, 2026

Family volume

$5K

Orderbook snapshot

26 / 39¢

Kalshi
13¢ spread
BidSize
26¢239
25¢37
22¢5
18¢150
17¢948
AskSize
39¢12
40¢125
41¢109
42¢432
45¢44

Contract terms

What resolves this market.

YES condition

If all teams collectively record at least 310 goals during the full tournament (including regulation, stoppage, and any extra time periods) of the 2026 Men's FIFA World Cup, then the market resolves to Yes.

Venue

Kalshi

Closes

Aug 3, 2026

Identifier

KXWCTOTALGOAL-26FT-310

SF Signal
SF Index
1014.16
Regime
neutral

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

1613.4%

IY (No)

467.8%

Adj IY

1014%

CRI

2

RV

2815%

VR

5.37

Regime

neutral

Score

0.5

Full indicator table

1613.4%
467.8%
Adj IY
1014%
2
RV
2815%
VR
5.37
IAR
2.8/h
Overround
2.6%
LAS
0.37

Related readings

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

Browse library
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

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.

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.

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.

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.