SimpleFunctions

Part Three Rotten Tomatoes score for Dune

Above 75 is priced at 90¢ on Kalshi. Current book: 87¢ bid, 92¢ ask, 5¢ spread. This outcome ranks #7 of 10 inside Dune: Part Three Rotten Tomatoes score?: Above.

Price history

90¢ current

+4¢
80¢90¢
Apr 24, 2026May 23, 2026

Contract brief

If Dune: Part Three has a Tomatometer score of above 75 on the Monday after wide release at 10:00 AM ET, then the market resolves to Yes.

Outcome

Above 75

Rank

#7 of 10

Leader

Above 50 99¢

Range

56¢-99¢

Family volume

$86

Identifier

KXRT-DUNE-75

May 23, 2026, 8:08 PM UTC · 19m ago

Implied probability

90¢
Latest venue quote
May 23, 2026, 8:08 PM UTC · 19m ago

Bid

87¢

Ask

92¢

Spread

24h volume

$11

Family rank

#7 of 10

10 outcomes · Dune: Part Three Rotten Tomatoes score?: Above

Closes

Dec 21, 2026

Family volume

$86

Orderbook snapshot

87 / 92¢

Kalshi
5¢ spread
BidSize
87¢31
86¢500
82¢500
80¢100
73¢100
AskSize
92¢500
93¢100
96¢500
97¢101
98¢200

Contract terms

What resolves this market.

YES condition

If Dune: Part Three has a Tomatometer score of above 75 on the Monday after wide release at 10:00 AM ET, then the market resolves to Yes.

Venue

Kalshi

Closes

Dec 21, 2026

Identifier

KXRT-DUNE-75

SF Signal
SF Index
576.69
Regime
neutral

Browse this series

Movie Rotten Tomatoes Score Markets
Per-series collection — every live contract in the KXRT series on Kalshi, sorted by 24h volume.

Indicators

Yield, cliff risk, volatility, and regime.

IY (Yes)

25.8%

IY (No)

1153.4%

Adj IY

577%

CRI

7

Overround

5.7%

Regime

neutral

Score

0.5

Full indicator table

25.8%
1153.4%
Adj IY
577%
7
Overround
5.7%

Related readings

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

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

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.

Conceptmethodology

Liquidity Migration Across Resolution: Where the Money Goes When a Market Closes

When a flagship prediction market closes, the capital that was in it migrates to next-period siblings, adjacent categories, or off the venue entirely. Three migration patterns and the receiving-market opportunity.

Conceptmethodology

Maker / Taker Regime in Prediction Markets: How to Read the Orderbook State

Three regime states (maker-dominated, taker-dominated, neutral) and how to read which one a Kalshi or Polymarket contract is in. Strategy follows regime, not thesis.

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.