SimpleFunctions

Tampa Bay wins by over 2.5 runs

Tampa Bay wins by over 2.5 runs is priced at 99¢ on Kalshi. Current book: 0¢ bid, 100¢ ask, 100¢ spread. This page tracks a standalone prediction-market contract.

Price history

99¢ current

+75¢
25¢50¢75¢100¢
May 6, 2026May 7, 2026

Contract brief

If Tampa Bay wins by more than 2.5 runs in the Tampa Bay vs Boston professional baseball game originally scheduled for May 7, 2026 at 7:10 PM EDT, then the market resolves to Yes.

Outcome

Tampa Bay wins by over 2.5 runs

Rank

Standalone

Leader

Range

Family volume

$128K

Identifier

KXMLBSPREAD-26MAY071910TBBOS-TB3

May 24, 2026, 10:20 PM UTC · 0m ago

Implied probability

99¢
Latest venue quote
May 24, 2026, 10:20 PM UTC · 0m ago

Bid

Ask

100¢

Spread

100¢

Reported volume

$128K

Family rank

Standalone

Standalone contract

Closes

May 8, 2026

Family volume

$128K

Orderbook snapshot

0 / 100¢

Kalshi
100¢ spread
No public depth snapshot is cached for this contract yet.

Contract terms

What resolves this market.

YES condition

If Tampa Bay wins by more than 2.5 runs in the Tampa Bay vs Boston professional baseball game originally scheduled for May 7, 2026 at 7:10 PM EDT, then the market resolves to Yes.

Venue

Kalshi

Closes

May 8, 2026

Identifier

KXMLBSPREAD-26MAY071910TBBOS-TB3

SF Signal
Regime
neutral

Event family

This market.

The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.

Total volume

$128K

Outcomes

1

Highest price

Tampa Bay wins by over 2.5 runs 99¢

Current share

100%

Indicators

Yield, cliff risk, volatility, and regime.

Regime

neutral

Score

0.5

Related readings

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

Browse library
Opinionessay

Prediction market liquidity: why depth matters more than volume for serious traders

Why orderbook depth matters more than volume for prediction market traders. Real Kalshi examples, liquidity scoring framework, and how to avoid slippage.

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.

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.

Opinionanalysis

Information Finance Has Arrived: A Material Map of Prediction Markets in Q2 2026

Combined Kalshi + Polymarket volume hit $66B in just four months of 2026 — already greater than the entire 2025 industry total. Bernstein projects $1T by 2030. Two venues hold 95% of US share. The distribution layer fragmented across nine retail surfaces. AI agents are 30% of Polymarket wallet activ

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.

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.

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.