What are prediction markets saying about yes Seattle wins by over 2.5 runs,no Over 7.5 runs scored?

As of the latest update, prediction markets are pricing yes Seattle wins by over 2.5 runs,no Over 7.5 runs scored at — across 1 platforms (kalshi). Total volume: $0.

How is the consensus probability calculated?

Consensus probability is the volume-weighted average YES probability across all matched markets on Polymarket, Kalshi, and Manifold. Markets without reported volume receive equal weight.

Why do prices differ between platforms?

Platforms have different fee structures, user bases, and liquidity pools, which creates small price differences even on the same event. Current spread: —.

Are prediction markets accurate?

Prediction markets have historically been well-calibrated for political and economic events, often outperforming traditional polling. Accuracy depends on liquidity and how close the market is to resolution.

yes Seattle wins by over 2.5 runs,no Over 7.5 runs scored

📅 Closes in -41 days

Platforms 1

Total Volume $0

Cross-platform spread —

Resolves 2026-04-28

Platform	Yes	No	Volume	Last seen	Link
Kalshi	—	—	—	23:24 UTC	View →
Kalshi	—	—	—	20:41 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	02:01 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	02:40 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	00:19 UTC	View →
Kalshi	—	—	—	06:31 UTC	View →
Kalshi	—	—	—	02:41 UTC	View →
Kalshi	—	—	—	02:25 UTC	View →
Kalshi	—	—	—	02:25 UTC	View →
Kalshi	—	—	—	02:41 UTC	View →
Kalshi	—	—	—	02:09 UTC	View →
Kalshi	—	—	—	23:56 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	00:22 UTC	View →
Kalshi	—	—	—	10:22 UTC	View →
Kalshi	—	—	—	20:33 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	07:41 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	07:33 UTC	View →
Kalshi	—	—	—	02:42 UTC	View →
Kalshi	—	—	—	01:47 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	07:25 UTC	View →
Kalshi	—	—	—	04:42 UTC	View →
Kalshi	—	—	—	20:42 UTC	View →
Kalshi	—	—	—	20:38 UTC	View →
Kalshi	—	—	—	08:49 UTC	View →
Kalshi	—	—	—	20:37 UTC	View →
Kalshi	—	—	—	02:39 UTC	View →
Kalshi	—	—	—	02:15 UTC	View →
Kalshi	—	—	—	01:55 UTC	View →
Kalshi	—	—	—	02:44 UTC	View →
Kalshi	—	—	—	00:19 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	11:41 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	04:42 UTC	View →
Kalshi	—	—	—	17:47 UTC	View →
Kalshi	—	—	—	00:36 UTC	View →
Kalshi	—	—	—	00:26 UTC	View →
Kalshi	—	—	—	23:06 UTC	View →
Kalshi	—	—	—	20:35 UTC	View →
Kalshi	—	—	—	02:09 UTC	View →
Kalshi	—	—	—	02:30 UTC	View →
Kalshi	—	—	—	05:12 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	04:23 UTC	View →
Kalshi	—	—	—	02:42 UTC	View →
Kalshi	—	—	—	20:37 UTC	View →
Kalshi	—	—	—	02:35 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	04:23 UTC	View →
Kalshi	—	—	—	01:43 UTC	View →
Kalshi	—	—	—	02:41 UTC	View →
Kalshi	—	—	—	17:58 UTC	View →
Kalshi	—	—	—	04:36 UTC	View →
Kalshi	—	—	—	02:24 UTC	View →
Kalshi	—	—	—	02:10 UTC	View →
Kalshi	—	—	—	08:15 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	02:44 UTC	View →
Kalshi	—	—	—	02:25 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	08:32 UTC	View →
Kalshi	—	—	—	07:32 UTC	View →
Kalshi	—	—	—	07:17 UTC	View →
Kalshi	—	—	—	20:37 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	02:09 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	02:40 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	02:12 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	08:31 UTC	View →
Kalshi	—	—	—	08:29 UTC	View →
Kalshi	—	—	—	12:13 UTC	View →
Kalshi	—	—	—	23:08 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	02:22 UTC	View →
Kalshi	—	—	—	02:08 UTC	View →
Kalshi	—	—	—	04:36 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	17:58 UTC	View →
Kalshi	—	—	—	02:22 UTC	View →
Kalshi	—	—	—	06:14 UTC	View →
Kalshi	—	—	—	04:31 UTC	View →
Kalshi	—	—	—	01:39 UTC	View →
Kalshi	—	—	—	02:40 UTC	View →
Kalshi	—	—	—	02:05 UTC	View →
Kalshi	—	—	—	04:43 UTC	View →
Kalshi	—	—	—	04:23 UTC	View →
Kalshi	—	—	—	05:52 UTC	View →
Kalshi	—	—	—	07:40 UTC	View →
Kalshi	—	—	—	07:40 UTC	View →
Kalshi	—	—	—	02:15 UTC	View →
Kalshi	—	—	—	02:26 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	00:36 UTC	View →
Kalshi	—	—	—	04:22 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	11:56 UTC	View →
Kalshi	—	—	—	04:37 UTC	View →
Kalshi	—	—	—	00:36 UTC	View →
Kalshi	—	—	—	04:23 UTC	View →
Kalshi	—	—	—	00:35 UTC	View →
Kalshi	—	—	—	00:32 UTC	View →
Kalshi	—	—	—	04:23 UTC	View →

No history yet — first few snapshots pending.

Probability history, most recent 30 days

What do these odds mean?

Cross-platform data for yes Seattle wins by over 2.5 runs,no Over 7.5 runs scored is still being collected.

How to read cross-platform spreads

When two platforms price the same event meaningfully differently, it usually means one of three things: liquidity is thin on one side, fee structures are pushing a spread, or traders on one platform have information the other lacks. Spreads larger than 5 percentage points on events with over $50K in volume often resolve toward the higher-volume platform's price.

About this data

Beeks.ai aggregates prediction market data from Polymarket, Kalshi, and Manifold. Updates run every minute. Consensus probability is a volume-weighted average across all matched markets. Historical snapshots are stored for calibration analysis.

Last updated: 2026-04-26 01:47:38 UTC · Download JSON

News & context

📰 Latest news on Google → 𝕏 Discussion on X → ⚡ All edge opportunities →

Your edge calculator

Enter your own probability estimate to see expected value and recommended position size using the Kelly Criterion.

Market price — Your estimate

50%

EV per $1: — · ¼ Kelly: — · Side: —