TOTAL VOLUME:

$134b

24H VOL:

$103,397,351

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,410,176,180

399,592

Markets across

30,097

events

MATCHED EVENTS:

2,622

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
Miami vs Philadelphia: First Inning Run
kalshi

Miami vs Philadelphia: First Inning Run

Volume:
$276,213

Yes

 - Kalshi

Yes - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Jun 16, 2026

Closed: Jun 16, 7:10 PM EST

kalshi

Kalshi

View
Join Kalshi and score $25 for your first trade.
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
kalshi

Yes

View
100%
Yes 100¢No 0¢
100¢
N/A
$276,213
N/A
N/A
$217,254
Settled
Yes
Total markets: 1

Description

This market tracks whether any run is scored during the opening inning of the Miami vs Philadelphia baseball matchup scheduled for June 16, 2026. First-inning scoring is a common occurrence in professional baseball and can set the tone for the game.

Kalshi

If either team scores a run in the first inning of the Miami vs Philadelphia professional baseball game originally scheduled for Jun 16, 2026 at 6:40 PM EDT, then the market resolves to Yes.

Frequently asked questions

On Kalshi, the first inning run market dashboard tracks real-time odds and historical price movements for whether Miami and Philadelphia will score in the opening inning of their matchup. The interface displays current market pricing, 24-hour trading volume via $258,158, and cumulative liquidity across all positions. Traders use this data to monitor how sentiment shifts as game time approaches, with the dashboard updating continuously to reflect new bets and order flow. This market captures pure prediction activity around a specific, measurable outcome tied to the earliest phase of play.

Prediction market odds and sportsbook odds often diverge because they serve different purposes and audiences. Sportsbooks set lines to balance action and lock in profit margins, while prediction markets like this one aggregate trader beliefs through continuous price discovery. Traders here are incentivized to identify mispricing relative to sportsbooks, meaning this market can sometimes lead or lag conventional betting lines depending on information flow and participation. The comparison reveals whether professional and amateur predictors see the first inning outcome differently than traditional oddsmakers.

On Kalshi, this market is priced through an order-book mechanism where traders buy and sell shares representing yes or no outcomes. On Kalshi, prices reflect that venue's order book, liquidity, and how traders price the outcome right now. Each share pays out a fixed amount if the outcome occurs, and the current bid-ask spread reflects the live consensus probability. Prices move as new orders flow in, allowing traders to enter or exit positions at any time before the market closes. The continuous repricing ensures the odds stay responsive to breaking news, betting patterns, and real-time game developments.

This market resolves around Jun 17, 2026, once the first inning concludes and the final run total is verifiable from credible public sources. The outcome hinges on whether at least one run crosses the plate during that inning for either team. Resolution is automatic once the official game record is available, with no manual intervention required. Traders should monitor live game feeds and official box scores as the deadline approaches to assess their positions.

Key catalysts include lineup announcements, starting pitcher confirmations, and weather or field conditions that might favor offensive play. Injury reports for star hitters or pitchers can shift expectations around early scoring. As game time nears, historical matchup data and recent team performance trends often drive repricing. Once play begins, the first few batters' plate appearances and any early baserunning activity will trigger sharp moves, with the market settling definitively once the inning ends and the run count is final.