Fagiano Okayama vs. Avispa Fukuoka: O/U 2.5
Probability
0¢
1h
+0.0pp
24h
-38.5pp
24h Vol
$6.8K
Liquidity
$57.4K
Probability (last 7 days)
-51.4pp 7dWhy 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
- 08:25SignalMEDIUM
Signal · Resolution risk
Market has reached expiry. Watch the UMA dispute window.
- 08:00PriceMEDIUM
Probability down -39.5pp
to 0¢
- 06:00PriceMEDIUM
Probability down -12.0pp
to 28¢
- 05:00PriceMEDIUM
Probability down -20.5pp
to 19¢
- 05:00ResolveHIGH
Market resolved 3h ago
- 03:00PriceMEDIUM
Probability down -5.5pp
to 34¢
- 02:00PriceMEDIUM
Probability down -5.5pp
to 34¢
- 00:00PriceMEDIUM
Probability down -6.0pp
to 34¢
- 23:00PriceMEDIUM
Probability down -7.5pp
to 34¢
- 21:00PriceMEDIUM
Probability down -6.5pp
to 35¢
- 20:00PriceMEDIUM
Probability down -6.0pp
to 35¢
- 18:00PriceMEDIUM
Probability down -5.5pp
to 36¢
- 14:00PriceMEDIUM
Probability down -3.5pp
to 38¢
- 13:00PriceMEDIUM
Probability down -3.5pp
to 38¢
- 1d agoPriceMEDIUM
Probability down -4.0pp
to 37¢
- 1d agoPriceMEDIUM
Probability down -12.0pp
to 37¢
- 2d agoPriceMEDIUM
Probability down -12.0pp
to 37¢
- 2d agoPriceMEDIUM
Probability down -12.0pp
to 40¢
- 2d agoPriceMEDIUM
Probability down -12.0pp
to 40¢
- 2d agoPriceMEDIUM
Probability down -12.0pp
to 40¢
- 2d agoPriceMEDIUM
Probability down -11.5pp
to 40¢
- 2d agoPriceMEDIUM
Probability down -13.5pp
to 40¢
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Related Markets
14- 100¢+82.0pp
Spread: Fagiano Okayama (-1.5)
AI · Vol $46.12
- 0¢-8.9pp
Spread: Avispa Fukuoka (-1.5)
Other · Vol $324.01
- 0¢-8.0pp
Spread: Fagiano Okayama (-2.5)
AI · Vol $4.8K
- 0¢-5.0pp
Spread: Avispa Fukuoka (-2.5)
Other · Vol $155.58
- 100¢+33.5pp
Fagiano Okayama vs. Avispa Fukuoka: O/U 1.5
AI · Vol $647.48
- 0¢-18.4pp
Fagiano Okayama vs. Avispa Fukuoka: O/U 3.5
AI · Vol $394.34
- 0¢-8.0pp
Fagiano Okayama vs. Avispa Fukuoka: O/U 4.5
AI · Vol $207.90
- 0¢-44.5pp
Fagiano Okayama vs. Avispa Fukuoka: Both Teams to Score
AI · Vol $775.47
- 10¢+4.3pp
Will OpenAI have the best AI model at the end of April 2026?
AI · Vol $392.1K
- 90¢-2.0pp
Will Anthropic have the best AI model at the end of April 2026?
AI · Vol $146.0K
- 0¢-0.2pp
Will DeepSeek have the best AI model at the end of April 2026?
AI · Vol $140.5K
- 0¢-0.5pp
Will Google have the best AI model at the end of April 2026?
AI · Vol $129.1K
- 0¢0.0pp
Will Baidu have the best AI model at the end of April 2026?
AI · Vol $117.4K
- 0¢0.0pp
Will the Orlando Magic win the 2026 NBA Finals?
AI · Vol $110.4K
Market Description
In the upcoming J1 100 Year Vision League game between Fagiano Okayama and Avispa Fukuoka, scheduled for April 25 at 1:00 AM ET: This market will resolve to "Over" if Fagiano Okayama and Avispa Fukuoka combine to score 3 or more goals in this game. If the combined total is less than 3, 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 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
HIGH risk- End date
- Apr 25, 2026
- UMA status
- proposed
- Resolution source
- https://www.jleague.jp/en/News consensus
- Market type
- Binary
- UMA status: proposed
- Market expires Apr 25, 2026 — dispute window active.
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).