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
Tour
All
Sports
Counter-Strike: ex-RUBY vs Metizport (BO3) - European Pro League Series 6 Playoffs
kalshi
polymarket

Counter-Strike: ex-RUBY vs Metizport (BO3) - European Pro League Series 6 Playoffs

Volume:
$213,549

Metizport

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 13, 2026

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

Metizport

View
100%
Yes 100¢No 0¢
—
N/A
$40,789
N/A
N/A
$23,881
Settled
Yes
polymarket

Match Winner

0%
Yes 0¢No 100¢
—
N/A
$81,773
N/A
N/A
N/A
Settled
No
polymarket

Map 1 Winner

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

O/U 2.5 Games

100%
Yes 100¢No 0¢
—
N/A
$5,670
N/A
N/A
N/A
Settled
Yes
polymarket

Odd/Even Total Rounds

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

Odd/Even Total Rounds

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

Odd/Even Total Rounds

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

Odd/Even Total Kills

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

ex-RUBY

0%
Yes 0¢No 100¢
—
N/A
$55,430
N/A
N/A
$36,944
Settled
No
polymarket

Map 2 Winner

0%
Yes 0¢No 100¢
—
N/A
$18,784
N/A
N/A
N/A
Settled
No
polymarket

Map Handicap: MZP (-1.5) vs ex-RUBY (+1.5)

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

Map Handicap: ex-RUBY (-1.5) vs Metizport (+1.5)

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

Odd/Even Total Kills

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

Odd/Even Total Kills

0%
Yes 0¢No 100¢
—
N/A
$20
N/A
N/A
N/A
Settled
No
Total markets: 14

Description

This event group covers a Counter-Strike Best-of-3 match between ex-RUBY and Metizport in the European Pro League Series 6 Playoffs Quarterfinals, scheduled for April 13, 2026 at 6:30 AM EDT. Markets span series outcome, individual map winners, map-level statistics (kills and rounds), and handicap bets across Kalshi and Polymarket platforms.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

All markets across both platforms use identical resolution hierarchy: official HLTV.org data with 2-hour credible reporting fallback, 50-50 for cancellations/delays beyond 7 days/incomplete series, and consistent treatment of forfeits, walkovers, and series clinches.Primary resolution logic: HLTV.org (official match results and statistics); credible reporting consensus (including video evidence) if HLTV.org does not publish within 2 hours of event conclusion

Core resolution logic:

  • Series Winner (ex-RUBY vs Metizport): Resolves to the team winning 2 maps in the BO3; if match is canceled, delayed beyond 7 days without play, or ends in forfeit/walkover before completion, resolves 50-50
  • Individual Map Winners (Map 1, 2, 3): Resolves to the team winning that map if play begins and the map concludes; resolves 50-50 if map is not played, not completed, or series clinches before that map is needed
  • Map Statistics (Odd/Even Kills, Odd/Even Rounds): Resolves based on completed map data if the map is played; resolves 50-50 if map is canceled, delayed beyond 7 days, not played due to forfeit/walkover/series clinch, or remade (resolution based on remade game only)
  • Games Total O/U 2.5: Resolves Over if 3+ maps are played (including forfeits/walkovers after play begins); resolves Under if fewer than 3 maps played; resolves 50-50 if match canceled, delayed beyond 7 days without winner, or incomplete series with forfeit/walkover
  • Map Handicap Markets: Resolves based on map differential (e.g., Metizport wins if they win 2+ more maps than ex-RUBY); forfeits/walkovers count if match is completed; resolves 50-50 if match canceled, delayed beyond 7 days, incomplete with forfeit/walkover, or ends in tie
  • Team Name Flexibility: Minor name variations, abbreviations, sponsor tags, and formatting differences are treated as referring to the same team; resolves 50-50 only if no reasonable connection exists or ambiguity prevents unique identification

Edge cases & clarifications:

  • Series Clinch Before Map Completion: If one team clinches the series (e.g., wins 2-0) before Map 3 is played, Map 3 statistics and Map 3 winner markets resolve 50-50. Games Total O/U 2.5 resolves Under (fewer than 3 maps played).
  • Forfeit or Walkover After Play Begins: If a team forfeits or walks over after the match has begun and the opponent wins, the series resolves to the winning team. Maps won by forfeit/walkover after play begins count toward series totals and handicap calculations. If forfeit/walkover occurs before any play, series resolves 50-50.
  • Map Remake: If a map is remade (e.g., due to technical issues), resolution is based solely on the remade game; the original game is disregarded.
  • Delay Beyond 7 Days: If the match is delayed beyond 7 days from the scheduled date (April 13, 2026) without play beginning, all markets resolve 50-50.
  • No Kills or Rounds Recorded: If a map is played but no kills are recorded (e.g., due to technical failure), Odd/Even Kills resolves 50-50. Odd/Even Rounds resolves based on actual rounds played.
Timing: Resolution occurs upon official publication by HLTV.org or within 2 hours after the match concludes via credible reporting consensus. Markets remain open until the match is completed 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.