Loading shell…
SportsExpires May 1, 2026

Madrid Open: Alexander Bublik vs Stefanos Tsitsipas

Probability

62¢

1h

+0.0pp

24h

+1.0pp

24h Vol

$41.2K

Liquidity

$169.4K

Probability (last 7 days)

+0.0pp 7d
Apr 23, 2026, 17:00Apr 25, 2026, 01:03
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 150.9h

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

Recent Trades

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

updated 0s ago·src:Polymarket Data

Market Description

This market refers to the tennis match between Alexander Bublik and Stefanos Tsitsipas in the Madrid Open, originally scheduled for April 24, 2026 at 4:00AM ET. This market will resolve to 'Alexander Bublik' if Alexander Bublik advances against Stefanos Tsitsipas. This market will resolve to 'Stefanos Tsitsipas' if Stefanos Tsitsipas advances against Alexander Bublik. If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50. If the match begins but is not completed, and one player advances due to the opponent's retirement, default, or disqualification, this market will resolve to the player who advances. If the match ends in a walkover (player withdraws before the start and the other advances automatically), this market will resolve to 50-50. The primary resolution source will be official information from the ATP Tour. A consensus of credible reporting may also be used.

Resolution & Risk

LOW risk
End date
May 1, 2026
UMA status
n/a
Resolution source
https://www.atptour.com/en/scores/currentNews consensus
Market type
Binary
  • No obvious resolution-risk signals in metadata.
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).