TOTAL VOLUME:

$134.2b

24H VOL:

$129,159,707

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,442,132,418

404,744

Markets across

30,489

events

MATCHED EVENTS:

2,691

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
Call of Duty: G2 Minnesota vs Cloud9 New York (BO5) - Call of Duty League Stage 2 Major Qualifiers Qualifiers
kalshi
polymarket

Call of Duty: G2 Minnesota vs Cloud9 New York (BO5) - Call of Duty League Stage 2 Major Qualifiers Qualifiers

Volume:
$184,277

G2 Minnesota

 - Kalshi

G2 Minnesota - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Feb 16, 2026

Closed: Feb 15, 11: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

G2 Minnesota

View
100%
Yes 100¢No 0¢
—
-$2,230
$35,476
N/A
N/A
$30,356
Settled
Yes
kalshi

Cloud9 New York

View
0%
Yes 0¢No 100¢
—
$2,840
$83,039
N/A
N/A
$69,900
Settled
No
polymarket

Match Winner

100%
Yes 100¢No 0¢
—
N/A
$28,435
0%
N/A
N/A
N/A
polymarket

Game Handicap: MIN (-2.5) vs Cloud9 New York (+2.5)

100%
Yes 100¢No 0¢
—
N/A
$11,092
0%
N/A
N/A
N/A
polymarket

Game 2 Winner

100%
Yes 100¢No 0¢
—
N/A
$10,782
0%
N/A
N/A
N/A
polymarket

Game 1 Winner

100%
Yes 100¢No 0¢
—
N/A
$3,236
0%
N/A
N/A
N/A
polymarket

Game Handicap: MIN (-1.5) vs Cloud9 New York (+1.5)

100%
Yes 100¢No 0¢
—
N/A
$1,337
0%
N/A
N/A
N/A
polymarket

Game 3 Winner

100%
Yes 100¢No 0¢
—
N/A
$1,253
0%
N/A
N/A
N/A
polymarket

O/U 3.5 Games

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

O/U 4.5 Games

0%
Yes 0¢No 100¢
—
N/A
$2,526
0%
N/A
N/A
N/A
Total markets: 10

Description

This event group covers a best-of-five Call of Duty League match between G2 Minnesota and Cloud9 New York scheduled for February 15, 2026, at 7:30 PM ET during the Stage 2 Major Qualifiers. Markets span individual game winners, series totals, handicaps, and the overall match outcome.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi provides only match-level binary resolution (either team wins = YES), while Polymarket offers game-level, total, and handicap markets with explicit 50-50 rules for incomplete games, forfeits, and walkovers. Kalshi's treatment of forfeits/walkovers is ambiguous compared to Polymarket's clarity.Hero tip: Polymarket markets are more granular and have explicit edge-case handling. For game-level or series-total bets, rely on Polymarket's 50-50 rules for incomplete/forfeit scenarios. For match outcome only, Kalshi is simpler but verify whether a forfeit/walkover counts as a win or triggers alternative resolution.

Critical divergence points:

  • Kalshi: Match-level binary resolution only. Resolves YES if either Cloud9 New York or G2 Minnesota wins the Call of Duty League Stage 2 Major Qualifiers match scheduled Feb 15, 2026. No game-level granularity. Forfeit/walkover treatment is not explicitly addressed in the provided rules.
  • Polymarket: Comprehensive game-level, series-total, and handicap markets. Individual game winners (Games 1, 2, 3) resolve based on completed game outcome or 50-50 if incomplete. Series totals (O/U 3.5, O/U 4.5) and handicaps (MIN -1.5, MIN -2.5) resolve 50-50 if match is canceled, delayed >7 days without play, or ends in forfeit/disqualification/walkover. Match winner resolves to the winning team if match begins and one team wins via forfeit/disqualification/walkover; resolves 50-50 if forfeit occurs before match start.
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.