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
Swansea City AFC vs. Southampton FC
polymarket
kalshi

Swansea City AFC vs. Southampton FC

Volume:
$236,840

Southampton FC

all

2 markets

Polymarket

Kalshi

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 18, 2026

Closed: Apr 18, 10:00 AM EST

polymarket

Polymarket

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

Southampton FC

View
100%
Yes 100¢No 0¢
—
N/A
$79,059
N/A
N/A
N/A
Settled
Yes
kalshi

Southampton

View
100%
Yes 100¢No 0¢
—
N/A
$59,458
N/A
N/A
$26,475
Settled
Yes
polymarket

Swansea City AFC

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

Swansea

View
0%
Yes 0¢No 100¢
—
N/A
$19,950
N/A
N/A
$13,257
Settled
No
kalshi

Tie

View
0%
Yes 0¢No 100¢
—
N/A
$26,488
N/A
N/A
$14,720
Settled
No
polymarket

Draw (Swansea City AFC vs. Southampton FC)

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

Description

This event is for the upcoming EFL Championship game, scheduled for Saturday, April 18, 2026 between Swansea City AFC and Southampton FC.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

All platforms resolve based on the official 90-minute match result (plus stoppage time) between Swansea City AFC and Southampton FC on April 18, 2026, with identical handling of postponements and cancellations across Polymarket and Kalshi.Primary resolution logic: Official EFL Championship statistics and governing body records, with fallback to credible reporting consensus if official statistics are not published within 2 hours of match conclusion.

Core resolution logic:

  • The three mutually exclusive outcomes are: Swansea City AFC wins, Southampton FC wins, or the match ends in a draw.
  • Each outcome resolves to YES on exactly one market per platform; all other outcome markets resolve to NO.
  • Resolution is based solely on the result after 90 minutes of regular play plus stoppage time, excluding extra time and penalties.
  • 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 resolves YES on Polymarket; Swansea and Southampton win markets resolve NO on both platforms.

Edge cases & clarifications:

  • Match Cancellation: On Polymarket, if the match is canceled entirely with no make-up game, the draw market resolves YES. On Kalshi, cancellation is not explicitly addressed, but the three outcome markets (Swansea win, Southampton win, Tie) collectively cover all logical possibilities, implying one must resolve YES.
  • Postponement and Rescheduling: Both platforms keep markets open if the match is postponed. Markets remain active until the rescheduled match is completed and the official result is recorded.
  • Source Timing Contingency: If the EFL does not publish official statistics within 2 hours of match conclusion, both platforms permit resolution based on consensus of credible reporting sources.
Timing: Resolution occurs upon official publication of the final match result by the EFL or governing body within 2 hours of match conclusion, or immediately upon consensus credible reporting 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.