TOTAL VOLUME:

$134b

24H VOL:

$107,351,958

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,416,970,024

400,720

Markets across

30,097

events

MATCHED EVENTS:

2,633

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

Counter-Strike: Phantom vs AM Gaming (BO1) - Parken Challenger Championship Group A

Volume:
$17,150

AM Gaming

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 18, 2026

Closed: Mar 31, 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

AM Gaming

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

Match Winner

View
0%
Yes 0¢No 100¢
—
N/A
$12,834
N/A
N/A
N/A
Settled
Yes
kalshi

Phantom

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

Odd/Even Total Rounds

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

Odd/Even Total Kills

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

Description

This event group covers a Counter-Strike: Global Offensive best-of-one match between Phantom and AM Gaming in the Parken Challenger Championship Group A, scheduled for March 31, 2026 at 9:00 AM ET. Markets track the match winner, Map 1 kill parity, and Map 1 round parity across Polymarket and Kalshi platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Polymarket defines three independent, granular markets with explicit edge-case rules and HLTV.org sourcing. Kalshi defines two markets that appear to collapse match outcome into a single Yes/No determination without specifying how forfeits, ties, delays, or incomplete series are handled, and without naming a resolution source.Hero tip: Treat Polymarket and Kalshi as separate resolution regimes. Polymarket markets are self-contained and will resolve based on HLTV.org data with clear 50-50 fallbacks. Kalshi markets lack sufficient detail to predict resolution in edge cases (e.g., if the match is forfeited, delayed >7 days, or if the series ends before Map 1 is played). Request clarification from Kalshi on source, forfeiture handling, and whether Map 1 must be played.

Critical divergence points:

  • Polymarket: Three independent markets: (1) Match Winner resolves to Phantom or AM Gaming if either wins; 50-50 on cancellation, tie, delay >7 days, or walkover. (2) Map 1 Kills Parity resolves Odd/Even based on combined kills; 50-50 if Map 1 not played or series decided. (3) Map 1 Rounds Parity resolves Odd/Even based on combined rounds; 50-50 if Map 1 not played or series decided. Source: HLTV.org with 2-hour credible consensus fallback. Key quote: 'If the match ends in a forfeit, disqualification, or walkover (team withdraws before the start and the other wins automatically), this market will resolve to 50-50.'
  • Kalshi: Two markets, both resolving to Yes if either AM Gaming or Phantom wins the match. No explicit edge-case rules for forfeits, ties, delays, or series non-completion. No resolution source specified. Markets appear to conflate match outcome with championship determination. Key quote: 'If AM Gaming wins the Parken Challenger Championship 2026: AM Gaming vs. Phantom CS2 match... then the market resolves to Yes.' (Identical logic for Phantom.)
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.