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: Alliance vs Nexus (BO1) - Roman Imperium Cup Group D
polymarket
kalshi

Counter-Strike: Alliance vs Nexus (BO1) - Roman Imperium Cup Group D

Volume:
$9,253

Nexus

 - Kalshi

Nexus - Kalshi

1W

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 18, 2026

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

Nexus

View
100%
Yes 100¢No 0¢
—
N/A
$5,029
N/A
N/A
$3,776
Settled
Yes
kalshi

Alliance

View
0%
Yes 0¢No 100¢
—
N/A
$4,224
N/A
N/A
$3,102
Settled
No
polymarket

Match Winner

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

Odd/Even Total Rounds

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

Odd/Even Total Kills

View
0%
Yes 0¢No 100¢
—
N/A
N/A
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 Alliance and Nexus in the Roman Imperium Cup Group D, scheduled for March 13, 2026 at 1:00 PM ET. Markets track the match winner, Map 1 round parity, and Map 1 kill parity across Polymarket and Kalshi platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Polymarket and Kalshi define fundamentally different market scopes and edge-case handling. Polymarket offers three linked markets with explicit 7-day delay thresholds and forfeit rules; Kalshi offers a single binary outcome with no delay or cancellation logic specified.Hero tip: Traders holding positions on both platforms should monitor HLTV.org for match delays, forfeits, or administrative changes. A delay beyond 7 days or a forfeit before match start will trigger 50-50 resolution on Polymarket but may leave Kalshi unresolved. Align your hedge strategy with the most conservative interpretation: assume Kalshi defaults to No if the match does not complete as scheduled.

Critical divergence points:

  • Polymarket: Three separate markets: (1) Match Winner resolves to Alliance or Nexus if either wins; 50-50 if canceled, tied, delayed >7 days, or forfeited before start. (2) Map 1 Rounds (Odd/Even) resolves based on total combined rounds; 50-50 if map not played, delayed >7 days, or series clinched early. (3) Map 1 Kills (Odd/Even) resolves based on total combined kills; 50-50 if no kills, map not played, delayed >7 days, or series clinched early. Primary source: HLTV.org within 2 hours; fallback to credible consensus with video evidence. Key Quote: 'If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50.'
  • Kalshi: Single binary market: resolves Yes if Alliance wins OR Nexus wins the match. No explicit handling of cancellations, ties, delays, or forfeits. No resolution source, timing criteria, or fallback logic specified. Key Quote: 'If Alliance wins the Roman Imperium Cup 2026: Nexus vs. Alliance CS2 match originally scheduled for Mar 13, 2026, then the market resolves to Yes. If Nexus wins the Roman Imperium Cup 2026: Nexus vs. Alliance CS2 match originally scheduled for Mar 13, 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.