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
Tour
All
Sports
Vejle BK vs. FC København
polymarket
kalshi

Vejle BK vs. FC København

Volume:
$93,041

Copenhagen

all

2 markets

Kalshi

Polymarket

consensus

News

Positive

Negative

Neutral

Hover marker for details

Vol.

·

Resolved Apr 19, 2026

Closed: Apr 19, 3:00 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

Copenhagen

View
100%
Yes 100¢No 0¢
—
N/A
$42,923
N/A
N/A
$24,391
Settled
Yes
polymarket

FC København

100%
Yes 100¢No 0¢
—
N/A
$16,891
N/A
N/A
N/A
Settled
Yes
kalshi

Tie

0%
Yes 0¢No 100¢
—
N/A
$14,123
N/A
N/A
$8,400
Settled
No
polymarket

Draw (Vejle BK vs. FC København)

0%
Yes 0¢No 100¢
—
N/A
$5,987
N/A
N/A
N/A
Settled
No
kalshi

Vejle

0%
Yes 0¢No 100¢
—
N/A
$7,271
N/A
N/A
$5,341
Settled
No
polymarket

Vejle BK

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

Description

Vejle BK and FC København will compete in a Danish Superligaen match on April 19, 2026. Three mutually exclusive outcomes are being traded: a Vejle BK win, an FC København win, or a draw. Settlement will be determined by the official final score after 90 minutes of regular play plus stoppage time.

PredictionHero - Resolution Divergence Alerts (RDA)

Unified Resolution Criteria (Consistent across platforms)

Both Polymarket and Kalshi use identical resolution logic: the market resolves based on the official match outcome after 90 minutes plus stoppage time on April 19, 2026, with consistent handling of postponements and cancellations.Primary resolution logic: Official statistics from the Danish Superliga (superligaen.dk) as recognized by the governing body or event organizers; if unavailable within 2 hours post-match, credible reporting consensus may be used.

Core resolution logic:

  • Vejle BK win market resolves YES if and only if Vejle BK wins the match within 90 minutes plus stoppage time.
  • FC København win market resolves YES if and only if FC København wins the match within 90 minutes plus stoppage time.
  • Draw market resolves YES if and only if the match ends in a draw within 90 minutes plus stoppage time.
  • Exactly one of the three markets will resolve YES; the other two resolve NO.
  • Extra time and penalties are excluded from resolution scope.
  • If the match is postponed, all markets remain open until the match is completed.
  • If the match is canceled with no make-up game, Vejle and Copenhagen win markets resolve NO, and the draw market resolves YES.

Edge cases & clarifications:

  • Match Postponement: If the match is postponed, all three markets remain open and unresolved until the rescheduled match is completed. Resolution then occurs based on the outcome of the completed match.
  • Match Cancellation: If the match is canceled entirely with no make-up game scheduled, the Vejle win and Copenhagen win markets resolve NO, while the draw market resolves YES.
  • Resolution Timing: Resolution is based on official Superliga statistics published within 2 hours after match conclusion. If official statistics are not available within 2 hours, credible reporting consensus is used as the fallback source.
Timing: Resolution occurs upon official publication of the final match result by the Danish Superliga or governing body, or upon consensus of credible reporting if official statistics are not published within 2 hours after the match concludes.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.