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
Counter-Strike: Omega vs Eternal Fire (BO3) - CCT Europe Series #18 Group Stage
kalshi
polymarket

Counter-Strike: Omega vs Eternal Fire (BO3) - CCT Europe Series #18 Group Stage

Volume:
$43,418

Map Handicap: EF (-1.5) vs Omega (+1.5)

 - Polymarket

Map Handicap: EF (-1.5) vs Omega (+1.5) - Polymarket

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 16, 2026

Closed: Mar 15, 5:10 PM EST

polymarket

Polymarket

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

Map Handicap: EF (-1.5) vs Omega (+1.5)

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

Odd/Even Total Kills

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

Match Winner

View
0%
Yes 0¢No 100¢
—
N/A
$29,715
N/A
N/A
N/A
Settled
No
polymarket

Map 1 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$9,715
N/A
N/A
N/A
Settled
No
polymarket

O/U 2.5 Games

View
0%
Yes 0¢No 100¢
—
N/A
$1,398
N/A
N/A
N/A
Settled
No
kalshi

Over 2.5 maps

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

Map 2 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$1,189
N/A
N/A
N/A
Settled
No
polymarket

Map Handicap: OMG (-1.5) vs Eternal Fire (+1.5)

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

Odd/Even Total Rounds

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

Odd/Even Total Rounds

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

Odd/Even Total Kills

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

Odd/Even Total Kills

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

Odd/Even Total Rounds

View
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: Global Offensive best-of-three (BO3) match between Omega and Eternal Fire in the CCT Europe Series #18 Group Stage, scheduled for March 15, 2026. Markets span match winner, individual map winners, map count totals, map handicaps, and odd/even kill and round counts across all three potential maps.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both platforms apply identical completion and forfeit logic, use HLTV.org as primary source, and resolve edge cases (cancellation, delay, incomplete play, ties) to 50-50 with consistent thresholds.Primary resolution logic: Official HLTV.org; credible reporting and video evidence if HLTV.org does not publish within 2 hours of event conclusion

Core resolution logic:

  • Match winner (Polymarket): resolves to the team that wins the BO3 series; 50-50 if canceled, tied, delayed beyond 7 days without winner, or incomplete without a decisive forfeit/disqualification
  • Individual map winners (Polymarket): resolve to the team winning that map if completed; 50-50 if map not played, not completed, or series already decided before that map
  • Map count over/under 2.5 (Kalshi): resolves Over if 3+ maps played, Under if fewer; 50-50 if canceled, tied, delayed beyond 7 days, or incomplete without decisive forfeit
  • Map handicap markets (Polymarket): EF (-1.5) resolves to Eternal Fire if EF wins 2+ more maps than Omega; OMG (-1.5) resolves to Omega if Omega wins 2+ more maps than EF; otherwise to opponent; 50-50 if canceled, tied, delayed, or incomplete without decisive forfeit
  • Odd/even kill and round markets (Polymarket): resolve based on completed map statistics; 50-50 if map not played, not completed, or series already decided before that map
  • Forfeit/disqualification/walkover: if match is completed via forfeit on the clinching map, it counts as a completed match for handicap and total map markets; if match begins but incomplete due to forfeit, those markets resolve 50-50; if forfeit occurs before match starts, match resolves 50-50

Edge cases & clarifications:

  • Incomplete match with decisive forfeit: If one team forfeits, is disqualified, or walks over after play has begun and the other team clinches the series, the match resolves to the winning team for match winner and handicap markets. However, if the match begins but is not completed and a forfeit occurs before a winner is determined, those markets resolve 50-50.
  • Pre-match forfeit or walkover: If a team withdraws or forfeits before the match starts, the match resolves 50-50 for all markets.
  • Map not played due to series clinch: If a team clinches the series before a map is needed (e.g., Map 3 not played after a 2-0 result), that map's markets resolve 50-50.
  • Delay beyond 7 days: If the match is delayed more than 7 days from the scheduled date (March 15, 2026) without a winner determined or play beginning, all markets resolve 50-50.
  • Tie or no result: If the match ends in a tie or no winner is determined for any reason other than the specific forfeit/disqualification scenarios, markets resolve 50-50.
Timing: Resolution occurs upon match completion or within 2 hours of event conclusion if HLTV.org publishes results; if HLTV.org does not publish within 2 hours, credible reporting and video evidence may be used. Markets resolve immediately upon determination of match outcome or upon confirmation that the match will not be completed or will be delayed beyond 7 days.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.