Loading shell…
OtherExpires Apr 11, 2026

Spread: Vissel Kōbe (-2.5)

Probability

1h

+0.0pp

24h

-0.2pp

24h Vol

$0.00

Liquidity

$1.2K

Probability (last 7 days)

+0.0pp 7d
Apr 18, 2026, 15:00Apr 25, 2026, 11:49
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
  • 11:49Signal

    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 J1 100 Year Vision League game, scheduled for April 11 at 2:00 AM ET: This market will resolve to "Vissel Kōbe" if Vissel Kōbe win the game by 3 or more goals. Otherwise, this market will resolve to "Nagoya Grampus". 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. This market will resolve according to the official final score published on jleague.jp. 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 11, 2026
UMA status
proposed
Resolution source
https://www.jleague.jp/en/News consensus
Market type
Binary
  • UMA status: proposed
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).