TOTAL VOLUME:

$134b

24H VOL:

$107,351,958

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,416,970,024

400,720

Markets across

30,097

events

MATCHED EVENTS:

2,633

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
1. FC Köln vs. Borussia Mönchengladbach
kalshi
polymarket

1. FC Köln vs. Borussia Mönchengladbach

Volume:
$677,950

Tie

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 21, 2026

Closed: Mar 21, 1:30 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

Tie

View
100%
Yes 100¢No 0¢
—
N/A
$91,928
N/A
N/A
$39,625
Settled
Yes
polymarket

Draw (1. FC Köln vs. Borussia Mönchengladbach)

View
100%
Yes 100¢No 0¢
—
N/A
$89,601
N/A
N/A
N/A
Settled
Yes
polymarket

1. FC Köln

View
0%
Yes 0¢No 100¢
—
N/A
$198,997
N/A
N/A
N/A
Settled
No
kalshi

FC Köln

View
0%
Yes 0¢No 100¢
—
N/A
$84,299
N/A
N/A
$46,577
Settled
No
kalshi

M´gladbach

View
0%
Yes 0¢No 100¢
—
N/A
$106,693
N/A
N/A
$47,448
Settled
No
polymarket

Borussia Mönchengladbach

View
0%
Yes 0¢No 100¢
—
N/A
$106,432
N/A
N/A
N/A
Settled
No
Total markets: 6

Description

This event is for the upcoming Bundesliga game, scheduled for Saturday, March 21, 2026 between 1. FC Köln and Borussia Mönchengladbach.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both Kalshi and Polymarket resolve based on the official outcome of the FC Köln vs. Borussia Mönchengladbach match scheduled for March 21, 2026, considering only the result after 90 minutes plus stoppage time, with the same primary source (official governing body statistics or credible consensus reporting).Primary resolution logic: Official Bundesliga statistics as recognized by the governing body; if unavailable within 2 hours of match conclusion, credible reporting consensus.

Core resolution logic:

  • Market resolves based on the final score after 90 minutes of regular play plus stoppage time (extra time and penalties are excluded).
  • Kalshi markets resolve YES if Köln wins, YES if a tie occurs, or YES if M'gladbach wins (all three outcomes trigger YES, making this a tautological market).
  • Polymarket markets resolve YES for Köln win, NO otherwise; YES for M'gladbach win, NO otherwise; and YES for a draw, NO otherwise (three separate binary markets covering all outcomes).
  • If the match is postponed, both platforms keep markets open until the match is completed.
  • If the match is canceled with no make-up game, Kalshi markets resolve YES (all outcomes covered) and Polymarket draw market resolves YES, while Polymarket win markets resolve NO.

Edge cases & clarifications:

  • Match Postponement: Both platforms keep their markets open until the match is completed, regardless of postponement duration.
  • Match Cancellation Without Makeup: Kalshi's tautological structure means all three markets resolve YES. Polymarket's draw market resolves YES; Polymarket's win markets resolve NO.
  • Official Statistics Delay: If Bundesliga does not publish final statistics within 2 hours of match conclusion, both platforms permit resolution based on credible reporting consensus.
Timing: Resolution occurs upon official Bundesliga announcement of the final match result, or within 2 hours after match conclusion via credible reporting if official statistics are delayed.Our PredictionHero Resolution Divergence Alerts (RDA) are there to help users identify potential differences across platforms. They do not replace or supersede the official rules and description of any prediction market. Users are solely responsible for reviewing and understanding the applicable rules and resolution criteria before placing any trade or bet. If you notice a potential inconsistency, discrepancy, or error in an alert, please report it to our team so we can review and improve the accuracy of our data.