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
Melbourne Victory FC vs. Newcastle United Jets FC
polymarket
kalshi

Melbourne Victory FC vs. Newcastle United Jets FC

Volume:
$487,734

Tie

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 17, 2026

Closed: Apr 17, 8:35 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

Tie

View
100%
Yes 100¢No 0¢
—
N/A
$58,665
N/A
N/A
$42,376
Settled
Yes
polymarket

Draw (Melbourne Victory FC vs. Newcastle United Jets FC)

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

Melbourne Victory FC

View
0%
Yes 0¢No 100¢
—
N/A
$129,738
N/A
N/A
N/A
Settled
No
kalshi

Melbourne Victory

View
0%
Yes 0¢No 100¢
—
N/A
$75,809
N/A
N/A
$40,235
Settled
No
kalshi

Newcastle

View
0%
Yes 0¢No 100¢
—
N/A
$100,940
N/A
N/A
$70,305
Settled
No
polymarket

Newcastle United Jets FC

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

Description

This event is for the upcoming Australia A-League game, scheduled for Friday, April 17, 2026 between Melbourne Victory FC and Newcastle United Jets FC.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

All platforms resolve based on the official match outcome (win, loss, or draw) within 90 minutes plus stoppage time on April 17, 2026, with consistent handling of postponements and cancellations.Primary resolution logic: Official A-League statistics as recognized by the governing body or event organizers (a-league.com.au); if unavailable within 2 hours post-match, credible reporting consensus may be used.

Core resolution logic:

  • Melbourne Victory Win market resolves YES if and only if Melbourne Victory wins within 90 minutes plus stoppage time; resolves NO otherwise or if game is canceled with no make-up.
  • Newcastle Jets Win market resolves YES if and only if Newcastle United Jets FC wins within 90 minutes plus stoppage time; resolves NO otherwise or if game is canceled with no make-up.
  • Draw market resolves YES if the match ends in a draw within 90 minutes plus stoppage time, or if the game is canceled entirely with no make-up; resolves NO if either team wins.
  • Exactly one of the three outcomes (Melbourne Victory win, Newcastle Jets win, or draw) will occur and resolve YES on one market only.
  • All markets remain open if the game is postponed until the match is completed.

Edge cases & clarifications:

  • Game Cancellation: If the game is canceled entirely with no make-up match, the Draw market resolves YES while both Win markets resolve NO.
  • Game Postponement: If the game is postponed, all markets remain open and unresolved until the match is completed on a rescheduled date.
  • Resolution Source Delay: If official A-League statistics are not published within 2 hours after match conclusion, resolution may be based on consensus of credible reporting sources.
Timing: Resolution occurs upon official publication of the final match result by the A-League or governing body, or within 2 hours post-match via credible reporting consensus if official sources are delayed.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.