Will ICEMAN debut No.1 on Billboard 200?
Probability
95¢
1h
+0.0pp
24h
+0.1pp
24h Vol
$426.54
Liquidity
$11.1K
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 2 factors- 1
Resolution-risk signal firing
Expires in 467h with open resolution ambiguity.
- 2
Thin liquidity
Only $11.1k of visible book — small orders can move the line. Treat the probability as a soft estimate.
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 467.1h
- 12:53SignalLOW
Signal · Resolution risk
Expires in 467h with open resolution ambiguity.
- 12:00PriceMEDIUM
Probability up 18.4pp
to 95¢
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Market Description
Drake's new album "ICEMAN" is expected to release in 2026. This market will resolve to "Yes" if Drake's next officially released album debuts at No. 1 on the Billboard 200 albums chart for its first charted week following release. Otherwise, this market will resolve to "No". If Drake does not release a new album by December 31, 2026, 11:59 PM ET, this market will resolve to "No". This market may resolve as soon as Billboard publishes the first chart week in which the album appears. The primary resolution source for this market will be information from Billboard (https://www.billboard.com/charts/billboard-200/).
Resolution & Risk
MEDIUM risk- End date
- May 15, 2026
- UMA status
- n/a
- Resolution source
- Not specified in metadata
- Market type
- Binary
- No primary resolution source listed — read the full market rules before acting.
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).