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
Insights
Indices
Tour
All
Trending
Breaking
New
Ending Soon
Politics
Sports
Crypto
Companies
Elections
Financials
Economics
Other
Entertainment
Science and Technology
SV Werder Bremen vs. FC Bayern München
polymarket
kalshi

SV Werder Bremen vs. FC Bayern München

Volume:
$4,798,093

Bayern Munich

 - Kalshi

Bayern Munich - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Feb 14, 2026

Closed: Feb 14, 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¢
—
$49,115
$1,170,568
N/A
N/A
$1,004,500
Settled
Yes
kalshi

Bremen

View
0%
Yes 0¢No 100¢
—
$39,634
$140,719
N/A
N/A
$113,882
Settled
No
kalshi

Tie

View
0%
Yes 0¢No 100¢
—
$56,901
$85,884
N/A
N/A
$75,188
Settled
No
polymarket

FC Bayern München

100%
Yes 100¢No 0¢
—
N/A
$2,343,727
0%
N/A
N/A
N/A
polymarket

SV Werder Bremen

0%
Yes 0¢No 100¢
—
N/A
$947,531
0%
N/A
N/A
N/A
polymarket

Draw (SV Werder Bremen vs. FC Bayern München)

0%
Yes 0¢No 100¢
—
N/A
$109,664
0%
N/A
N/A
N/A
Total markets: 6

Description

This event group covers the Bundesliga match between SV Werder Bremen and FC Bayern München scheduled for February 14, 2026. Markets track three mutually exclusive outcomes: a Bremen win, a Bayern win, or a draw, all resolved based on the result after 90 minutes plus stoppage time.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both Polymarket and Kalshi apply identical resolution windows (90 minutes plus stoppage time, no extra time or penalties) and recognize the same three mutually exclusive outcomes, with only minor differences in cancellation handling that do not affect the core match result logic.Primary resolution logic: Official Bundesliga match records and final scoreline after 90 minutes plus stoppage time

Core resolution logic:

  • Match result is determined by the official score after 90 minutes of regular play plus stoppage time
  • Three mutually exclusive outcomes: SV Werder Bremen win, FC Bayern München win, or draw
  • Extra time and penalty shootouts are excluded from resolution scope
  • If match is postponed, all markets remain open until the rescheduled match is completed
  • If match is canceled with no makeup game scheduled, Polymarket resolves draw market to Yes and win markets to No; Kalshi treats as pending rescheduling

Edge cases & clarifications:

  • Match Postponement: If the match is postponed, all markets remain open and unresolved until the rescheduled match is completed. Resolution then occurs based on the final result of the completed match.
  • Match Cancellation Without Makeup: Polymarket: draw market resolves Yes, Bremen win resolves No, Bayern win resolves No. Kalshi: structure implies markets remain open pending rescheduling, but cancellation without makeup is treated as an edge case requiring manual adjudication.
  • Scope Boundary: Resolution is strictly limited to the result after 90 minutes plus stoppage time. Any result determined in extra time or via penalty shootout is outside the resolution scope and does not apply.
Timing: Resolution occurs immediately after the match concludes (at the end of 90 minutes plus stoppage time on February 14, 2026, or on the rescheduled date if postponed)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.