SimpleFunctions
9 contractsKalshirefreshed 6 min agoCloses Oct 31, 2028 · 912d

Will Chicago win the 2026 Pro Basketball Draft Lottery

Liquidity-weighted aggregate sits at 10% across 9 Kalshi contracts.

Implied probability

10%
0%50%100%

Kalshi

10%

9 contracts

Polymarket

not bound

Cross-venue gap

single venue

24h move

no pin

24h volume

$5K

9 contracts

Closes

Oct 31, 2028

912 days

30-day trend

0%50%100%-30d-3w-2w-1wtodayAggregate: 8% (21 days, 21 points)Aggregate: 8% on 2026-04-30
Aggregate of 9 contracts · 21d

Bracket families

9 clusters across 9 contracts.

These contracts were grouped by title similarity. The headline aggregate combines all clusters; verify the cluster you actually need before quoting a number.

Cluster 1

Will Utah win the 2026 Pro Basketball Draft Lottery

1 contract$4K

Cluster 2

Will Chicago win the 2026 Pro Basketball Draft Lottery

1 contract$182

Cluster 3

Will Washington win the 2026 Pro Basketball Draft Lottery

1 contract$135

Cluster 4

Will Brooklyn win the 2026 Pro Basketball Draft Lottery

1 contract$132

Cluster 5

Will Indiana win the 2026 Pro Basketball Draft Lottery

1 contract$121

Cluster 6

Will Dallas win the 2026 Pro Basketball Draft Lottery

1 contract$28

Cluster 7

Will Atlanta win the 2026 Pro Basketball Draft Lottery

1 contract$0

Cluster 8

Will Memphis win the 2026 Pro Basketball Draft Lottery

1 contract$0

Cluster 9

Will Sacramento win the 2026 Pro Basketball Draft Lottery

1 contract$0

Analysis

The 10% probability reflects market expectations that Chicago has a one-in-ten chance of winning the 2026 NBA Draft Lottery. The lottery determines draft order based on weighted odds favoring teams with worse records, and Chicago's relatively low probability suggests traders believe the team is not among the worst-performing teams entering the lottery drawing. The lottery drawing date would provide the definitive resolution, as it mechanically determines winners regardless of prior expectations. Movements in this probability would likely respond to actual season standings changes, injuries to key players affecting win-loss records, or significant roster transactions that alter team competitiveness heading into the lottery calculation period.

  • Chicago's current NBA standings position relative to other lottery teams—worse records receive higher odds, so teams ranking bottom-3 would have substantially higher probabilities
  • Whether Chicago makes roster moves or trades before the lottery cutoff that could impact their final season record and lottery odds weighting
  • The health status of key Chicago players, particularly star-level contributors whose availability directly affects win-loss outcomes
  • Market pricing across related contracts shows San Antonio (23¢) and Philadelphia (13¢) as favorites in their respective categories, suggesting differentiated confidence in outcomes affecting lottery positioning
  • The lottery drawing mechanism is fixed by rule, making this a pure odds-based probability dependent entirely on final standings determination

Recently closed in general

These markets stopped trading. Last odds and any captured outcome are shown above — full settlement detail lives at the venue.

More like this

Adjacent prediction questions.

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.

Last updated on this page: 6 min ago.