TOTAL VOLUME:

$134.1b

24H VOL:

$133,388,117

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,436,095,462

405,232

Markets across

30,526

events

MATCHED EVENTS:

2,693

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
NK Slaven Belupo vs. HNK Hajduk Split
polymarket
kalshi

NK Slaven Belupo vs. HNK Hajduk Split

Volume:
$212,944

Tie

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 17, 2026

Closed: Apr 17, 2:45 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

Tie

View
100%
Yes 100¢No 0¢
—
N/A
$72,944
N/A
N/A
$44,376
Settled
Yes
polymarket

Draw (NK Slaven Belupo vs. HNK Hajduk Split)

View
100%
Yes 100¢No 0¢
—
N/A
$2,393
N/A
N/A
N/A
Settled
Yes
kalshi

Hajduk

View
0%
Yes 0¢No 100¢
—
N/A
$67,495
N/A
N/A
$42,330
Settled
No
polymarket

HNK Hajduk Split

View
0%
Yes 0¢No 100¢
—
N/A
$2,622
N/A
N/A
N/A
Settled
No
kalshi

Slaven Belupo

View
0%
Yes 0¢No 100¢
—
N/A
$66,841
N/A
N/A
$36,661
Settled
No
polymarket

NK Slaven Belupo

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

Description

NK Slaven Belupo will face HNK Hajduk Split in a Croatian HNL (First Football League) match scheduled for April 17, 2026. The market outcome is determined by the final score after 90 minutes of regular play plus stoppage time, excluding extra time or penalties. This is a standard three-way soccer outcome event (home win, draw, away win).

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both Polymarket and Kalshi resolve based on the official match outcome after 90 minutes plus stoppage time on April 17, 2026, with identical treatment of postponements and cancellations across all three possible outcomes (Belupo win, draw, Hajduk win).Primary resolution logic: Official statistics from the Croatian Football League (HNL) as recognized by the governing body, or consensus of credible reporting if official statistics are not published within 2 hours after match conclusion.

Core resolution logic:

  • Market resolves based on the match result after 90 minutes of regular play plus stoppage time, excluding extra time and penalties.
  • Three mutually exclusive outcomes are possible: NK Slaven Belupo wins, draw, or HNK Hajduk Split wins.
  • If the match is postponed, all markets remain open until the match is completed.
  • If the match is canceled with no make-up game, Belupo win and Hajduk win markets resolve NO, while the draw market resolves YES.

Edge cases & clarifications:

  • Postponement Protocol: If the match is postponed, all markets remain open and unresolved until the rescheduled match is completed. Resolution occurs only after the completed match result is official.
  • Cancellation Without Makeup: If the match is canceled entirely with no make-up game scheduled, the draw market resolves YES while both win markets (Belupo and Hajduk) resolve NO.
  • Resolution Source Hierarchy: Primary source is official HNL statistics. If official statistics are not published within 2 hours after match conclusion, a consensus of credible reporting sources may be used instead.
Timing: Resolution occurs upon official publication of the final match result by the Croatian Football League or, if delayed, upon consensus of credible reporting within 2 hours after match conclusion.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.