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: Rune Eaters vs Basement Bobs (BO3) - European Pro League Series 6 Group B
kalshi
polymarket

Counter-Strike: Rune Eaters vs Basement Bobs (BO3) - European Pro League Series 6 Group B

Volume:
$34,720

Basement Bobs

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Mar 29, 2026

Closed: Mar 29, 10:30 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

Basement Bobs

View
100%
Yes 100¢No 0¢
—
N/A
$3,220
N/A
N/A
$2,655
Settled
Yes
polymarket

Match Winner

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

Odd/Even Total Rounds

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

Odd/Even Total Kills

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

Map Handicap: BB (-1.5) vs Rune Eaters (+1.5)

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

Map 2 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$10,981
N/A
N/A
N/A
Settled
No
polymarket

Map 1 Winner

View
0%
Yes 0¢No 100¢
—
N/A
$7,906
N/A
N/A
N/A
Settled
No
kalshi

Rune Eaters

View
0%
Yes 0¢No 100¢
—
N/A
$2,596
N/A
N/A
$2,559
Settled
No
polymarket

Odd/Even Total Kills

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

Odd/Even Total Rounds

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

Map Handicap: RE (-1.5) vs Basement Bobs (+1.5)

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

O/U 2.5 Games

View
0%
Yes 0¢No 100¢
—
N/A
$51
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: 14

Description

This event group covers a best-of-three Counter-Strike match between Rune Eaters and Basement Bobs in the European Pro League Series 6 Group B, scheduled for March 29, 2026 at 6:30 AM ET. Markets span match winner, individual map winners, map-level statistics (rounds and kills), series handicaps, and total games played, with resolution sourced primarily from HLTV.org.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Polymarket and Kalshi share identical resolution sources (HLTV.org primary, credible consensus secondary), contingency triggers (cancellation, 7-day delay, incomplete play, series clinch), and edge case handling across all match and map-level markets.Primary resolution logic: Official HLTV.org reporting; if not published within 2 hours of event conclusion, credible consensus reporting including video evidence may be used.

Core resolution logic:

  • Match winner resolves to the team that wins the best-of-three series (first to 2 map wins).
  • Individual map winners resolve based on the team that wins that specific map in regulation or overtime.
  • Map statistics (total rounds, total kills) resolve based on the sum of both teams' performance in that map, including overtime rounds and all valid kills (excluding team kills and self-inflicted deaths).
  • Series handicap RE (-1.5) resolves to Rune Eaters if they win 2+ more maps than Basement Bobs; otherwise to Basement Bobs.
  • Series handicap BB (-1.5) resolves to Basement Bobs if they win 2+ more maps than Rune Eaters; otherwise to Rune Eaters.
  • Games Total O/U 2.5 resolves Over if 3+ maps are played, Under if fewer than 3 maps are played.
  • Odd/Even markets resolve based on whether the total (rounds or kills) is an odd or even number.

Edge cases & clarifications:

  • Match Canceled or Delayed Beyond 7 Days: All markets resolve 50-50 if the match is not played at all or is delayed beyond 7 days from the scheduled date (March 29, 2026) without play beginning.
  • 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 2-0), that map's markets (winner, rounds, kills) resolve 50-50. Series-level markets resolve to the clinching team.
  • Forfeit, Disqualification, or Walkover: If the match ends due to forfeit/disqualification/walkover before play begins, all markets resolve 50-50. If the match begins and one team forfeits mid-series, completed maps count toward resolution; incomplete maps resolve 50-50. If the clinching map is forfeited, the series result counts as completed.
  • Incomplete Map with Winner Determined: If a map begins but is not completed and a winner is determined (e.g., Map 1 concluded but series abandoned), that map's winner market resolves to the determined winner; statistics markets resolve 50-50 if data is incomplete.
  • Kalshi Anomaly - Both Outcomes Resolve Yes: Kalshi's market states both Rune Eaters and Basement Bobs winning resolve to Yes. This is a logical error in the market definition and should be clarified with the platform; it does not affect Polymarket resolution but creates ambiguity on Kalshi.
Timing: Resolution occurs within 2 hours of the match conclusion (expected March 29, 2026, 6:30 AM ET + match duration). If HLTV.org does not publish within 2 hours, credible consensus reporting may be used immediately thereafter. Markets remain pending until the match is played or the 7-day delay threshold is exceeded.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.