Loading shell…
OtherMulti-outcomeExpires May 31, 2026

Will Slovan Liberec win Czechia Fortuna Liga?

Probability

1h

+0.0pp

24h

+0.0pp

24h Vol

$0.00

Liquidity

$3.4K

Probability (last 7 days)

+0.0pp 7d
Apr 18, 2026, 07:00Apr 25, 2026, 01:13
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 866.8h

    LOW
  • 01:13Signal

    Signal · Resolution risk

    Expires in 867h with open resolution ambiguity.

    LOW
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

This market will resolve to "Yes" if the listed club is determined as the champion of the Czechia Fortuna Liga. Otherwise, it will resolve to "No". If at any point it becomes impossible for a listed participant to be named as the champion of Czechia Fortuna Liga per the rules of Czechia Fortuna Liga (e.g., participant is eliminated), the corresponding market will resolve to "No". If multiple teams are declared winners, this market will resolve in favor of the team whose listed name comes first alphabetically. If this event is cancelled, postponed after May 31, 2026, 11:59 PM ET, or a champion has not been declared within this timeframe, this market will resolve to "Other". The resolution source will be official information from the Czechia Fortuna Liga; however a consensus of credible reporting may also be used.

Resolution & Risk

LOW risk
End date
May 31, 2026
UMA status
n/a
Resolution source
credible reportingNews consensusextracted · medium
Market type
Multi-outcome (neg-risk)
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).