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
Çaykur Rizespor vs. Gaziantep FK
polymarket
kalshi

Çaykur Rizespor vs. Gaziantep FK

Volume:
$583,814

Çaykur Rizespor

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 14, 2026

Closed: Apr 13, 1:00 PM EST

polymarket

Polymarket

View
Outcome
Trade
Chance %
Price
Spread
Liquidity
Volume
24h
7d
Open Interest
Ends in
Result
polymarket

Çaykur Rizespor

View
100%
Yes 100¢No 0¢
—
N/A
$307,766
N/A
N/A
N/A
Settled
Yes
kalshi

Rizespor

View
100%
Yes 100¢No 0¢
—
N/A
$81,435
N/A
N/A
$22,467
Settled
Yes
polymarket

Gaziantep FK

View
0%
Yes 0¢No 100¢
—
N/A
$74,033
N/A
N/A
N/A
Settled
No
kalshi

Gaziantep

View
0%
Yes 0¢No 100¢
—
N/A
$62,902
N/A
N/A
$33,365
Settled
No
kalshi

Tie

View
0%
Yes 0¢No 100¢
—
N/A
$30,281
N/A
N/A
$18,328
Settled
No
polymarket

Draw (Çaykur Rizespor vs. Gaziantep FK)

View
0%
Yes 0¢No 100¢
—
N/A
$27,397
N/A
N/A
N/A
Settled
No
Total markets: 6

Description

This event is for the upcoming Süper Lig game, scheduled for Monday, April 13, 2026 between Çaykur Rizespor and Gaziantep FK.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Polymarket structures three mutually exclusive binary markets (Rizespor win, Draw, Gaziantep win) where exactly one resolves YES, while Kalshi structures three independent markets where ALL THREE can resolve YES simultaneously depending on the match outcome. This creates a fundamental logical contradiction: the same match result cannot satisfy Polymarket's exclusivity constraint and Kalshi's independence constraint at the same time.Hero tip: Do not assume these markets are equivalent across platforms. On Polymarket, exactly one of the three outcomes will resolve YES. On Kalshi, exactly one of the three outcomes will also resolve YES, but the market structure treats them as independent events rather than mutually exclusive options. If you trade across both platforms, verify your hedge logic carefully—a YES bet on Polymarket's draw market and a YES bet on Kalshi's draw market are structurally different propositions.

Critical divergence points:

  • Polymarket: Outlier: Polymarket offers three separate binary markets (Rizespor win, Draw, Gaziantep win) with mutually exclusive resolution logic. Exactly one market will resolve YES and the other two will resolve NO. The draw market uniquely resolves YES if the game is canceled with no make-up, while the win markets resolve NO in that scenario. Key quote: 'If the game is canceled entirely, with no make-up game, this market will resolve to Yes' (draw) vs. 'this market will resolve to No' (win markets).
  • Kalshi: Distinct stance: Kalshi presents three independent binary markets framed as 'If [outcome] wins...then the market resolves to Yes,' treating each outcome as a standalone event rather than mutually exclusive options. All three markets reference the same match but are logically independent; exactly one will resolve YES based on the actual result, but the market structure does not enforce mutual exclusivity in the resolution rules themselves. Key quote: 'If Rizespor wins...then the market resolves to Yes. If Gaziantep wins...then the market resolves to Yes. If Tie wins...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.