Loading shell…
OtherMulti-outcomeExpires Apr 15, 2026

Will CS Huancayo win on 2026-04-15?

Probability

1h

+0.0pp

24h

+0.0pp

24h Vol

$0.00

Liquidity

$12.2K

Probability (last 7 days)

+0.0pp 7d
Apr 18, 2026, 00:00Apr 24, 2026, 23:19
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
  • 23:19Signal

    Signal · Resolution risk

    Market has reached expiry. Watch the UMA dispute window.

    LOW
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 game, scheduled for April 15, 2026 If CS Huancayo wins, this market will resolve to "Yes". Otherwise, this market will resolve to "No". 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 "No". 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

MEDIUM risk
End date
Apr 15, 2026
UMA status
proposed
Resolution source
https://liga1.pe/News consensus
Market type
Multi-outcome (neg-risk)
  • UMA status: proposed
  • Part of a multi-outcome event (neg-risk): only one market can resolve YES.
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).