TOTAL VOLUME:

$134.2b

24H VOL:

$129,159,707

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,442,132,418

404,744

Markets across

30,489

events

MATCHED EVENTS:

2,691

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
Brisbane Roar FC vs. Sydney FC
kalshi
polymarket

Brisbane Roar FC vs. Sydney FC

Volume:
$382,394

Tie

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 2, 2026

Closed: Apr 2, 9:00 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
$54,868
N/A
N/A
$42,884
Settled
Yes
polymarket

Draw (Brisbane Roar FC vs. Sydney FC)

View
100%
Yes 100¢No 0¢
—
N/A
$43,973
N/A
N/A
N/A
Settled
Yes
polymarket

Brisbane Roar FC

View
0%
Yes 0¢No 100¢
—
N/A
$95,200
N/A
N/A
N/A
Settled
No
kalshi

Brisbane

View
0%
Yes 0¢No 100¢
—
N/A
$29,264
N/A
N/A
$24,367
Settled
No
polymarket

Sydney FC

View
0%
Yes 0¢No 100¢
—
N/A
$85,403
N/A
N/A
N/A
Settled
No
kalshi

Sydney FC

View
0%
Yes 0¢No 100¢
—
N/A
$73,686
N/A
N/A
$57,983
Settled
No
Total markets: 6

Description

Brisbane Roar FC and Sydney FC will compete in an A-League match on April 2, 2026. This event group captures three mutually exclusive outcomes: a Brisbane Roar victory, a Sydney FC victory, or a draw. All markets measure the result after 90 minutes of regular play plus stoppage time, excluding extra time and penalties.

PredictionHero - Resolution Divergence Alerts (RDA)

Divergence Detected

Issue: Kalshi's three markets collectively cover all possible outcomes (Brisbane win, Sydney win, or draw) and each resolves to Yes for its respective outcome, creating logical contradiction where exactly one market must resolve Yes. Polymarket's three markets are mutually exclusive binary outcomes (Brisbane Yes/No, Sydney Yes/No, Draw Yes/No) with standard resolution logic. The platforms use fundamentally incompatible resolution architectures.Hero tip: Do not trade across both platforms assuming they settle identically. Kalshi's structure guarantees exactly one market resolves Yes (the actual match result), while Polymarket's structure allows only one of three markets to resolve Yes based on standard binary logic. If you hold positions on both platforms, verify the actual match outcome will map consistently—it should, but Kalshi's unusual wording creates settlement risk. Prioritize Polymarket for clarity; Kalshi's phrasing is ambiguous and may cause disputes.

Critical divergence points:

  • Kalshi: Outlier: Uses a three-market structure where each market resolves Yes if its specific outcome occurs (Brisbane wins → Market 1 Yes; Tie → Market 2 Yes; Sydney wins → Market 3 Yes). This guarantees exactly one market resolves Yes. The resolution rule states 'If [outcome] wins the Brisbane vs Sydney FC professional Australia A League soccer game... then the market resolves to Yes,' creating a logical architecture where all three markets share identical resolution timing and source but are outcome-dependent.
  • Polymarket: Aligned with standard binary market logic: Three separate binary markets (Brisbane Win Yes/No, Sydney Win Yes/No, Draw Yes/No) where each resolves independently based on whether its named outcome occurs. Resolution source is official A-League statistics within 2 hours post-match, or credible consensus if unavailable. Postponement keeps markets open; cancellation with no makeup resolves Draw market to Yes, others to No. All three markets refer to 90 minutes plus stoppage time only.
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.