TOTAL VOLUME:

$134.1b

24H VOL:

$133,388,117

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,436,095,462

405,232

Markets across

30,526

events

MATCHED EVENTS:

2,693

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: Vitality vs Aurora Gaming (BO3) - PGL Cluj-Napoca Playoffs
polymarket
kalshi

Counter-Strike: Vitality vs Aurora Gaming (BO3) - PGL Cluj-Napoca Playoffs

Volume:
$1,800,775

Vitality

 - Kalshi

Vitality - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Feb 20, 2026

Closed: Feb 20, 1:00 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

Vitality

View
100%
Yes 100¢No 0¢
—
N/A
$121,867
N/A
N/A
$97,685
Settled
Yes
kalshi

Aurora Gaming

View
0%
Yes 0¢No 100¢
—
N/A
$137,987
N/A
N/A
$119,978
Settled
No
polymarket

Match Winner

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

Map 1 Winner

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

Map 2 Winner

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

Map Handicap: VIT (-1.5) vs Aurora Gaming (+1.5)

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

O/U 2.5 Games

0%
Yes 0¢No 100¢
—
N/A
$22,950
0%
N/A
N/A
N/A
Total markets: 7

Description

This event group covers a Counter-Strike best-of-three match between Vitality and Aurora Gaming at PGL Cluj-Napoca Playoffs scheduled for February 20, 2026 at 9:00 AM ET. Markets span individual map winners, match outcome, map handicap, and total maps played, with resolution sourced primarily from HLTV.org.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Polymarket defines detailed edge cases (forfeits, incomplete matches, delays) with 50-50 fallbacks, while Kalshi provides minimal guidance. Additionally, Polymarket's Map Handicap and Total Maps markets contain a logical ambiguity regarding whether a forfeit victory constitutes a 'completed match' for counting purposes.Hero tip: Before trading Polymarket's Map Handicap or Total Maps markets, confirm with the platform whether a 1-0 forfeit victory counts as match completion and whether maps won by forfeit are included in the count. For Kalshi, assume any decisive outcome (including forfeit) resolves Yes; if the match is canceled or delayed beyond 7 days without play, request clarification on the 50-50 fallback.

Critical divergence points:

  • Polymarket: Five distinct markets with explicit edge-case handling. Map 1 and Map 2 resolve 50-50 if not completed; Match Winner resolves 50-50 if canceled, delayed beyond 7 days, or ends in forfeit/disqualification. Map Handicap and Total Maps count forfeit/disqualification maps only if match is 'completed,' but resolve 50-50 if match begins but is incomplete due to forfeiture—creating logical ambiguity. All resolve via HLTV.org within 2 hours, or credible reporting consensus if delayed. Key Quote: 'Maps won by forfeit, disqualification, walkover, or default are counted towards the handicap, provided that the match is completed.'
  • Kalshi: Single binary market: resolves Yes if either Vitality or Aurora Gaming wins the match originally scheduled for Feb 20, 2026. No explicit handling of cancellations, delays, forfeits, or disqualifications. Implicitly assumes a winner will be determined. Key Quote: 'If Vitality wins the PGL Cluj-Napoca 2026: Aurora Gaming vs. Vitality CS2 match originally scheduled for Feb 20, 2026, then the market resolves to Yes.'
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.