TOTAL VOLUME:

$134.2b

24H VOL:

$130,522,377

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,438,389,636

404,028

Markets across

30,214

events

MATCHED EVENTS:

2,681

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
Counter-Strike: K27 vs CYBERSHOKE Esports (BO3) - Stake Ranked Episode 1: Closed Qualifier Playoffs
polymarket
kalshi

Counter-Strike: K27 vs CYBERSHOKE Esports (BO3) - Stake Ranked Episode 1: Closed Qualifier Playoffs

Volume:
$69,251

Match Winner

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 4, 2026

Closed: Mar 4, 12:00 PM EST

polymarket

Polymarket

View
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

Match Winner

View
100%
Yes 100¢No 0¢
—
N/A
$26,046
N/A
N/A
N/A
Settled
Yes
kalshi

K27

View
100%
Yes 100¢No 0¢
—
N/A
$19,656
N/A
N/A
$11,842
Settled
Yes
polymarket

Map 1 Winner

View
100%
Yes 100¢No 0¢
—
N/A
$3,406
N/A
N/A
N/A
Settled
Yes
polymarket

O/U 2.5 Games

View
100%
Yes 100¢No 0¢
—
N/A
$261
N/A
N/A
N/A
Settled
Yes
kalshi

CYBERSHOKE Esports

View
0%
Yes 0¢No 100¢
—
N/A
$11,321
N/A
N/A
$8,312
Settled
No
polymarket

Map 2 Winner

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

Map Handicap: K27 (-1.5) vs CYBERSHOKE Esports (+1.5)

View
0%
Yes 0¢No 100¢
—
N/A
$1,071
N/A
N/A
N/A
Settled
No
Total markets: 7

Description

This event group covers a Counter-Strike Best-of-3 match between K27 and CYBERSHOKE Esports in the Stake Ranked Episode 1: Closed Qualifier Playoffs, scheduled for March 4, 2026 at 6:00 AM ET. Markets span match winner, individual map winners (Map 1 and Map 2), total maps played, and map handicap outcomes across Polymarket and Kalshi platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi's market structure is incomplete and does not address edge cases (forfeits, cancellations, delays). Polymarket provides comprehensive granular markets with explicit 50-50 resolution rules for non-completion scenarios. The two platforms are not directly comparable as markets.Hero tip: Treat Polymarket as the authoritative resolution source for this event. Polymarket's match winner market explicitly resolves 50-50 on pre-match forfeits, cancellations, or delays beyond 7 days. Kalshi's binary structure does not clarify these scenarios. Monitor HLTV.org for official results within 2 hours of match conclusion; if delayed, Polymarket permits consensus from credible reporting and video evidence.

Critical divergence points:

  • Polymarket: Five distinct markets (match winner, Map 1 winner, Map 2 winner, total maps O/U 2.5, map handicap -1.5/+1.5) with explicit edge-case logic. Match winner resolves 50-50 if match is canceled, delayed beyond 7 days without play, or ends in pre-match forfeit/disqualification/walkover. If match begins and opponent forfeits mid-series, the winning team is declared. Maps won by forfeit/disqualification/walkover count toward totals and handicap if match is completed. Resolution source: HLTV.org within 2 hours; fallback to credible reporting and video evidence.
  • Kalshi: Single binary market: resolves Yes if K27 wins OR Yes if CYBERSHOKE Esports wins. No explicit edge-case handling provided for cancellations, delays, forfeits, or incomplete matches. Market structure implies automatic Yes resolution but does not clarify what happens if match does not occur or is abandoned.
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.