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: WAZABI vs maquinas (BO1) - Parken Challenger Championship Group A
kalshi
polymarket

Counter-Strike: WAZABI vs maquinas (BO1) - Parken Challenger Championship Group A

Volume:
$17,781

Match Winner

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 1, 2026

Closed: Mar 31, 7:30 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
$14,934
N/A
N/A
N/A
Settled
Yes
kalshi

WAZABI

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

Odd/Even Total Kills

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

maquinas

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

Odd/Even Total Rounds

View
0%
Yes 0¢No 100¢
—
N/A
$21
N/A
N/A
N/A
Settled
No
Total markets: 5

Description

This event group covers a Counter-Strike BO1 match between WAZABI and maquinas in the Parken Challenger Championship Group A, scheduled for March 31, 2026. Markets track the match winner, plus Map 1 statistics (total kills odd/even and total rounds odd/even). Resolution depends on official HLTV.org reporting and handles edge cases like cancellations, forfeits, and delays.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both Kalshi and Polymarket align on HLTV.org as primary source, apply identical 7-day delay threshold, and treat forfeits/walkovers/series-clinch scenarios consistently as 50-50 outcomes.Primary resolution logic: HLTV.org (official); credible consensus reporting with video evidence if HLTV.org unavailable within 2 hours of match conclusion

Core resolution logic:

  • Match winner (WAZABI vs maquinas): resolves to the team that wins the BO1 match
  • Map 1 total kills odd/even: resolves based on combined kills from both teams, excluding team kills and self-inflicted deaths
  • Map 1 total rounds odd/even: resolves based on sum of rounds won by both teams, including overtime if applicable
  • Cancellation or no-play scenarios: if match is canceled, not played, or delayed beyond 7 days without completion, all markets resolve 50-50
  • Forfeit/walkover/disqualification before play: match winner resolves 50-50; Map 1 markets resolve 50-50
  • Series clinch before Map 1: if series result determined before Map 1 is needed, Map 1 markets resolve 50-50
  • Remade games: if Map 1 is remade, resolution uses remade game data only

Edge cases & clarifications:

  • Match delayed beyond 7 days: All markets resolve 50-50 if match is delayed beyond 7 days from scheduled date (March 31, 2026) without a winner determined
  • Forfeit or walkover before play: Match winner resolves 50-50; Map 1 kills and rounds resolve 50-50
  • Series clinch before Map 1: Map 1 kills and rounds resolve 50-50 if series result already determined before Map 1 is needed
  • Map 1 remade: Resolution uses remade game data only; original game data is disregarded
  • No kills recorded in Map 1: Map 1 kills odd/even resolves 50-50 if zero kills recorded
Timing: Resolution occurs within 2 hours after match conclusion based on official HLTV.org publication; if HLTV.org unavailable, consensus reporting with video evidence is used as fallbackOur 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.