TOTAL VOLUME:

$134.2b

24H VOL:

$134,145,987

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,441,166,947

406,422

Markets across

30,383

events

MATCHED EVENTS:

2,688

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
1. FSV Mainz 05 vs. FC Bayern München
kalshi
polymarket

1. FSV Mainz 05 vs. FC Bayern München

Volume:
$5,352,286

Bayern Munich

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 25, 2026

Closed: Apr 25, 12: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

Bayern Munich

View
100%
Yes 100¢No 0¢
—
N/A
$2,342,146
N/A
N/A
$1,302,564
Settled
Yes
polymarket

FC Bayern München

100%
Yes 100¢No 0¢
—
N/A
$1,345,954
N/A
N/A
N/A
Settled
Yes
kalshi

Mainz

0%
Yes 0¢No 100¢
—
N/A
$518,256
N/A
N/A
$252,929
Settled
No
polymarket

1. FSV Mainz 05

0%
Yes 0¢No 100¢
—
N/A
$394,622
N/A
N/A
N/A
Settled
No
kalshi

Tie

0%
Yes 0¢No 100¢
—
N/A
$453,829
N/A
N/A
$156,336
Settled
No
polymarket

Draw (1. FSV Mainz 05 vs. FC Bayern München)

0%
Yes 0¢No 100¢
—
N/A
$297,479
N/A
N/A
N/A
Settled
No
Total markets: 6

Description

This event group covers the Bundesliga match between 1. FSV Mainz 05 and FC Bayern München scheduled for April 25, 2026. Polymarket offers three binary markets (Mainz win, Draw, Bayern win), while Kalshi offers a single market covering all three outcomes. Both platforms resolve based on the result after 90 minutes of regular play plus stoppage time, excluding extra time and penalties.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

All platforms resolve based on the official match outcome after 90 minutes plus stoppage time on April 25, 2026, with identical handling of postponement (markets remain open) and cancellation (Mainz/Bayern markets resolve NO, draw market resolves YES).Primary resolution logic: Official Bundesliga statistics and governing body records, with fallback to credible reporting consensus if official statistics unavailable within 2 hours of match conclusion.

Core resolution logic:

  • Market resolves based on the match outcome within 90 minutes of regular play plus stoppage time only, excluding extra time and penalties.
  • Exactly one of the three outcome markets (Mainz win, draw, Bayern win) will resolve YES; the other two resolve NO.
  • If the match is postponed, all markets remain open until the match is completed.
  • If the match is canceled with no make-up game, Mainz win and Bayern win markets resolve NO, while the draw market resolves YES.

Edge cases & clarifications:

  • Postponement Protocol: If the match is postponed, all three markets remain open and unresolved until the rescheduled match is completed and the outcome is determined.
  • Cancellation Resolution: If the match is canceled entirely with no make-up game scheduled, the draw market resolves YES while both win markets (Mainz and Bayern) resolve NO.
  • Resolution Source Hierarchy: Primary source is official Bundesliga and governing body statistics. If official statistics are not published within 2 hours after match conclusion, resolution uses consensus from credible reporting sources.
Timing: Resolution occurs upon official publication of final match statistics by Bundesliga or governing body, or within 2 hours after match conclusion via credible reporting consensus 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.