Loading shell…
OtherMulti-outcomeExpires Dec 6, 2026

Will Esteban Ocon be the 2026 F1 Drivers' Champion?

Probability

1h

+0.0pp

24h

-0.1pp

24h Vol

$158.1K

Liquidity

$803.1K

Probability (last 7 days)

-0.1pp 7d
Apr 17, 2026, 20:00Apr 24, 2026, 19:48
updated 0s ago·src:Polymarket CLOB

Why did it move?

 

Without an Anthropic API key we show a heuristic summary derived from the market metrics.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 0s agoResolve

    Market resolves in 5404.2h

    LOW
  • 19:49Signal

    Signal · Resolution risk

    Expires in 5404h with open resolution ambiguity.

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

Active signals

Recent Trades

25
updated 0s ago·src:Polymarket Data

Market Description

This market will resolve according to the listed driver that finishes 1st in the driver standings for the 2026 F1 season. This market will resolve as soon as the official results of the final scheduled race of the 2026 F1 season are known. If multiple drivers tie for first place in the drivers standings, this market will resolve according to the tiebreak procedure used by F1 to determine the 2026 F1 Drivers’ champion. If at any point it becomes impossible for a listed driver to win the 2026 F1 Drivers Championship based on the rules of F1 (e.g., they are mathematically eliminated from contention), the corresponding market will resolve to “No”. If the F1 season is permanently canceled or has not been completed by March 31, 2027, 11:59 PM ET, this market will resolve to “Other”. The primary resolution source for this market will be official information from Formula 1.

Resolution & Risk

MEDIUM risk
End date
Dec 6, 2026
Resolution source
UMA status
n/a
Market type
Multi-outcome (neg-risk)
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
  • No primary resolution source listed — read the market rules.
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).