Loading shell…
SportsMulti-outcomeExpires May 31, 2026

Will Brentford place 17th for the 2025-26 English Premier League season?

Probability

15¢

1h

+0.0pp

24h

+0.0pp

24h Vol

$0.00

Liquidity

$111.39

Probability (last 7 days)

+0.0pp 7d
Apr 18, 2026, 11:00Apr 25, 2026, 10:55
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 853.1h

    LOW
  • 10:55Signal

    Signal · Resolution risk

    Expires in 853h 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 team finishes 17th in the 2025-26 English Premier League. Otherwise, the associated market will resolve to "No". If at any point it becomes impossible for the listed team to finish 17th in the 2025-26 English Premier League (e.g. they mathematically cannot finish in 17th), the associated market will resolve to "No". If the 2025-2026 English Premier League season is cancelled, postponed after May 31, 2026, 11:59 PM ET, or there is otherwise no 17th place team declared within that timeframe, this market will resolve to “Other”. The resolution source for this market will be official information from the EPL; 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
Not specified in metadata
Market type
Multi-outcome (neg-risk)
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
  • Wide spread (30.0¢) — liquidity risk on entry/exit.
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).