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
Tour
All
Sports
Counter-Strike: ex-RUBY vs Lavked (BO3) - CCT Europe Series #19 Playoffs
kalshi
polymarket

Counter-Strike: ex-RUBY vs Lavked (BO3) - CCT Europe Series #19 Playoffs

Volume:
$136,433

Lavked

 - Kalshi

Lavked - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 1, 2026

Closed: Apr 1, 8:00 AM 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

Lavked

View
100%
Yes 100¢No 0¢
—
N/A
$22,884
N/A
N/A
$16,222
Settled
Yes
polymarket

Odd/Even Total Kills

100%
Yes 100¢No 0¢
—
N/A
$347
N/A
N/A
N/A
Settled
Yes
polymarket

Match Winner

0%
Yes 0¢No 100¢
—
N/A
$46,338
N/A
N/A
N/A
Settled
No
kalshi

ex-RUBY

0%
Yes 0¢No 100¢
—
N/A
$40,413
N/A
N/A
$33,795
Settled
No
polymarket

Map 1 Winner

0%
Yes 0¢No 100¢
—
N/A
$18,313
N/A
N/A
N/A
Settled
No
polymarket

Map 2 Winner

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

O/U 2.5 Games

0%
Yes 0¢No 100¢
—
N/A
$340
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Rounds

0%
Yes 0¢No 100¢
—
N/A
$325
N/A
N/A
N/A
Settled
No
polymarket

Map Handicap: ex-RUBY (-1.5) vs Lavked (+1.5)

0%
Yes 0¢No 100¢
—
N/A
$214
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Rounds

0%
Yes 0¢No 100¢
—
N/A
$213
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Kills

0%
Yes 0¢No 100¢
—
N/A
$30
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Kills

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
polymarket

Odd/Even Total Rounds

N/A
N/A
—
N/A
N/A
N/A
N/A
N/A
Settled
No
Total markets: 13

Description

This event group covers a Counter-Strike 2 best-of-three match between ex-RUBY and Lavked in the CCT Europe Series #19 Playoffs, scheduled for April 1, 2026 at 4:00 AM EDT. Markets span match winner, individual map winners, and granular statistics (rounds and kills per map), with resolution sourced from HLTV.org.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi provides minimal resolution criteria (binary Yes/No on match outcome only), while Polymarket offers comprehensive edge-case handling for forfeits, walkovers, cancellations, delays, and incomplete matches. This creates divergent outcomes in non-standard scenarios.Hero tip: Prioritize Polymarket's detailed rules as the authoritative framework. If the match faces cancellation, delay beyond 7 days, or forfeit/walkover before play, expect Polymarket to resolve 50-50. Kalshi's ambiguity in these scenarios makes it higher-risk. Verify match status on HLTV.org within 2 hours of scheduled conclusion.

Critical divergence points:

  • Kalshi: Binary Yes/No resolution: 'If Lavked wins... then Yes' and 'If ex-RUBY wins... then Yes'. No explicit rules for forfeits, walkovers, cancellations, delays, or incomplete matches. Ambiguous whether a forfeit/walkover counts as a 'win' for resolution purposes.
  • Polymarket: Comprehensive edge-case rules: Forfeits/walkovers/disqualifications before play begins resolve 50-50; incomplete matches with one team winning by opponent forfeiture resolve 50-50; cancellations or delays beyond 7 days without a winner resolve 50-50. 'If the match ends due to the clinching map being forfeited this will count as a completed match.' Explicit 2-hour HLTV.org publication window before consensus reporting is used.
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.