TOTAL VOLUME:

$134.1b

24H VOL:

$141,541,542

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,440,096,988

406,065

Markets across

30,522

events

MATCHED EVENTS:

2,692

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Insights
Indices
Tour
All
Trending
Breaking
New
Ending Soon
Politics
Sports
Crypto
Companies
Elections
Financials
Economics
Other
Entertainment
Science and Technology
Minnesota vs Detroit: 9th Inning Total
kalshi

Minnesota vs Detroit: 9th Inning Total

Volume:
$0

Over 0.5 runs in the 9th inning

 - Kalshi

Over 0.5 runs in the 9th inning - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Sep 7, 2026

Closed: Sep 7, 5:45 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

Over 0.5 runs in the 9th inning

View
N/A
N/A
100¢
N/A
N/A
N/A
N/A
N/A
Settled
No
kalshi

Over 1.5 runs in the 9th inning

View
N/A
N/A
100¢
N/A
N/A
N/A
N/A
N/A
Settled
No
Total markets: 2

Description

This market focuses on predicting whether a specific baseball game between Minnesota and Detroit will see a certain number of runs scored in the final inning. It tracks the combined scoring performance of both teams exclusively during the ninth inning, providing insight into late-game offensive dynamics. The outcome depends solely on the runs accumulated in that inning, regardless of the game's final result.

Kalshi

The event determines whether the combined total runs scored by Minnesota and Detroit in the ninth inning of their professionally scheduled game on September 7, 2026, exceed specified thresholds of 0.5 or 1.5 runs. Only runs scored during the ninth inning are counted, and the resolution applies even if the home team does not complete its at-bat, provided the inning begins. If the game is called early before the ninth inning is fully completed, the market resolves to a Fair Price. The markets are independent of each other, each resolving based on its respective run threshold.