SimpleFunctions

Doomsday Rotten Tomatoes score for Avengers

Above 80 is priced at 63¢ on Kalshi. Current book: 59¢ bid, 63¢ ask, 4¢ spread. This outcome ranks #8 of 10 inside Avengers: Doomsday Rotten Tomatoes score?: Above.

Price history

63¢ current

+4¢
60¢
Apr 25, 2026May 16, 2026

Contract brief

If Avengers: Doomsday has a Tomatometer score of above 80 on the Monday after wide release at 10:00 AM ET, then the market resolves to Yes.

Outcome

Above 80

Rank

#8 of 10

Leader

Above 45 95¢

Range

28¢-95¢

Family volume

$109

Identifier

KXRT-AVE-80

May 24, 2026, 10:38 PM UTC · 24m ago

Implied probability

63¢
Latest venue quote
May 24, 2026, 10:38 PM UTC · 24m ago

Bid

59¢

Ask

63¢

Spread

24h volume

$30

Family rank

#8 of 10

10 outcomes · Avengers: Doomsday Rotten Tomatoes score?: Above

Closes

Dec 21, 2026

Family volume

$109

Orderbook snapshot

59 / 63¢

Kalshi
4¢ spread
BidSize
59¢9
57¢500
53¢500
52¢100
45¢100
AskSize
63¢2
64¢574
65¢498
68¢500
69¢200

Contract terms

What resolves this market.

YES condition

If Avengers: Doomsday has a Tomatometer score of above 80 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-AVE-80

SF Signal
SF Index
124.65
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)

120.4%

IY (No)

249.3%

Adj IY

125%

CRI

1

Overround

6.3%

Regime

neutral

Score

0.409

Observability

medium

Event type

cultural

Full indicator table

120.4%
249.3%
Adj IY
125%
1
Overround
6.3%

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.

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.

Opinionanalysis

Implied Yield vs Raw Probability: Why Bond-Adjacent Prediction Markets Need a Different Lens

Why fixed-income-adjacent prediction-market contracts need to be priced in implied yield, not raw probability, with two real Kalshi Fed-decision contracts as a case study.

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.