TOTAL VOLUME:

$134.2b

24H VOL:

$126,324,530

24H TRANSACTIONS:

2,388,728,490

OPEN INTEREST:

$1,434,646,834

406,019

Markets across

30,401

events

MATCHED EVENTS:

2,689

PLATFORM COVERAGE:

5

Polymarket:

39%

VS.

Kalshi:

61%

BETA
Dashboards
Tour
All
Sports
Real Salt Lake vs. Sporting Kansas City
polymarket
kalshi

Real Salt Lake vs. Sporting Kansas City

Volume:
$516,922

Real Salt Lake

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 5, 2026

Closed: Apr 4, 4:30 PM EST

polymarket

Polymarket

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

Real Salt Lake

View
100%
Yes 100¢No 0¢
—
N/A
$181,002
N/A
N/A
N/A
Settled
Yes
kalshi

Salt Lake

100%
Yes 100¢No 0¢
—
N/A
$100,339
N/A
N/A
$45,045
Settled
Yes
kalshi

Kansas City

0%
Yes 0¢No 100¢
—
N/A
$127,522
N/A
N/A
$80,684
Settled
No
polymarket

Sporting Kansas City

0%
Yes 0¢No 100¢
—
N/A
$18,493
N/A
N/A
N/A
Settled
No
kalshi

Tie

0%
Yes 0¢No 100¢
—
N/A
$63,827
N/A
N/A
$41,659
Settled
No
polymarket

Draw (Real Salt Lake vs. Sporting Kansas City)

0%
Yes 0¢No 100¢
—
N/A
$25,738
N/A
N/A
N/A
Settled
No
Total markets: 6

Description

This event group covers the Major League Soccer match between Real Salt Lake and Sporting Kansas City scheduled for April 4, 2026. The markets assess three mutually exclusive outcomes: a Real Salt Lake victory, a Sporting Kansas City victory, or a draw. All resolutions are based on the result after 90 minutes of regular play plus stoppage time, excluding extra time or penalties.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Polymarket and Kalshi both resolve based on the official MLS match result for Real Salt Lake vs. Sporting Kansas City on April 4, 2026, considering only the outcome within 90 minutes plus stoppage time, with identical handling of postponements and cancellations.Primary resolution logic: Official MLS Soccer statistics and records (mlssoccer.com) as recognized by the governing body; if unavailable within 2 hours post-match, credible reporting consensus may be used.

Core resolution logic:

  • The match outcome is determined solely by the result after 90 minutes of regular play plus stoppage time (no extra time or penalties).
  • Exactly one of three mutually exclusive outcomes will occur: Real Salt Lake wins, Sporting Kansas City wins, or the match ends in a draw.
  • If the match is postponed, all markets remain open until the match is completed.
  • If the match is canceled with no make-up game, the draw market (Polymarket) resolves YES, while the win markets (both platforms) resolve NO.
  • Each platform offers complementary markets covering all three possible outcomes, with exactly one market resolving YES per match completion.

Edge cases & clarifications:

  • Postponement: If the match is postponed, all markets remain open and unresolved until the rescheduled match is completed. Resolution occurs based on the final result of the completed match.
  • Cancellation Without Make-Up: If the match is canceled entirely with no make-up game scheduled, Polymarket's draw market resolves YES (treating cancellation as a draw outcome), while all win markets on both platforms resolve NO.
  • Source Fallback: If official MLS statistics are not published within 2 hours after match conclusion, resolution may be determined by consensus of credible reporting sources.
Timing: Resolution occurs immediately upon official publication of the final match result by MLS or, if necessary, within 2 hours post-match based on credible reporting consensus.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.