Musk out as Tesla CEO before 2027?
Probability
8¢
1h
+0.0pp
24h
-0.5pp
24h Vol
$36.60
Liquidity
$12.9K
Probability (last 7 days)
-1.0pp 7dWhy did it move?
Structured · 2 factors- 1
Resolution-risk signal firing
Expires in 5987h with open resolution ambiguity.
- 2
Thin liquidity
Only $12.9k of visible book — small orders can move the line. Treat the probability as a soft estimate.
What to track next
- Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
Verification actions only — never trade recommendations.
Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.
AI prose summary
Prose narration of the same metrics shown in the structured breakdown above. Cites only the market data on this page — no news, no predictions. Use the structured factors as the canonical answer; this is here for readability.
Timeline — news, trades, signals, price moves
- 0s agoResolveLOW
Market resolves in 5987.0h
- 13:00SignalLOW
Signal · Resolution risk
Expires in 5987h with open resolution ambiguity.
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Market Description
This market will resolve to "Yes" if Elon Musk ceases to be CEO of Tesla for any length of time between November 11, 2025, and December 31, 2026 11:59PM ET. Otherwise, this market will resolve to "No". An announcement of Elon Musk's resignation/firing before this market's end date will immediately resolve this market to "Yes", regardless of when the announced resignation/firing goes into effect. This market's primary resolution source will be official information from Tesla and/or Elon Musk, however a consensus of credible reporting will also be used.
Resolution & Risk
LOW risk- End date
- Dec 31, 2026
- UMA status
- n/a
- Resolution source
- Not specified in metadata
- Market type
- Binary
- No obvious resolution-risk signals in metadata.
Alerts
In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).