Loading shell…
OtherExpires Apr 25, 2026

D.C. United SC vs. Orlando City SC: O/U 3.5

Probability

30¢

1h

+0.0pp

24h

-0.5pp

24h Vol

$1.8K

Liquidity

$10.9K

Probability (last 7 days)

+0.0pp 7d
Apr 18, 2026, 17:00Apr 25, 2026, 15:39
updated 0s ago·src:Polymarket CLOB

Why did it move?

Structured · 3 factors
  1. 1

    Resolution-risk signal firing

    Expires in 8h with open resolution ambiguity.

  2. 2

    Thin liquidity

    Only $10.9k of visible book — small orders can move the line. Treat the probability as a soft estimate.

  3. 3

    Expiry in 8h

    Market resolves within 72 hours — the move likely reflects information about the resolution event itself rather than longer-horizon repricing. Verify the resolution source.

What to track next

  • Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
  • Set an alert for resolution status changes — expiry is in 8 hours.

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

AllTradesSignalsPrice
  • 23:30Resolve

    Market resolves in 7.8h

    HIGH
  • 15:40Signal

    Signal · Resolution risk

    Expires in 8h with open resolution ambiguity.

    LOW
  • 15:00Price

    Probability down -3.5pp

    to 30¢

    MEDIUM
  • 14:00Price

    Probability down -4.0pp

    to 30¢

    MEDIUM
  • 12:00Price

    Probability down -3.0pp

    to 31¢

    MEDIUM
  • 09:00Price

    Probability down -4.5pp

    to 30¢

    MEDIUM
  • 08:00Price

    Probability down -6.5pp

    to 30¢

    MEDIUM
  • 06:00Price

    Probability down -6.5pp

    to 30¢

    MEDIUM
  • 05:00Price

    Probability down -7.0pp

    to 30¢

    MEDIUM
  • 03:00Price

    Probability down -5.5pp

    to 30¢

    MEDIUM
  • 00:00Price

    Probability down -8.0pp

    to 31¢

    MEDIUM
  • 23:00Price

    Probability down -3.0pp

    to 30¢

    MEDIUM
  • 1d agoPrice

    Probability up 3.5pp

    to 33¢

    MEDIUM
  • 1d agoPrice

    Probability up 3.0pp

    to 33¢

    MEDIUM
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

In the upcoming MLS game between D.C. United SC and Orlando City SC, scheduled for April 25 at 7:30 PM ET: This market will resolve to "Over" if D.C. United SC and Orlando City SC combine to score 4 or more goals in this game. If the combined total is less than 4, this market will resolve to "Under". If the game is postponed, this market will remain open until the game has been completed. If the game is canceled entirely, with no make-up game, this market will resolve 50–50. If the game is started but not completed, this market will resolve according to the official final score published on mlssoccer.com. This market refers only to the outcome within the first 90 minutes of regular play plus stoppage time. The primary resolution source for this market is the official statistics of the event as recognized by the governing body or event organizers. However, if the governing body or event organizers have not published final match statistics within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead.

Resolution & Risk

HIGH risk
End date
Apr 25, 2026
UMA status
n/a
Resolution source
https://www.mlssoccer.com/schedule/scoresNews consensus
Market type
Binary
  • Market expires Apr 25, 2026 — dispute window active.
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).