Spread: FC Augsburg (-1.5)
Probability
20¢
1h
+1.0pp
24h
+1.0pp
24h Vol
$7.3K
Liquidity
$53.0K
Probability (last 7 days)
+1.0pp 7dWhy did it move?
Structured · 4 factors- 1
Up 1pp over 24h
Now 20¢; +1.0pp in the last hour.
- 2
Light volume — move on a thin book
Only $7.3k traded against $53.0k of visible liquidity (0.14× turnover). Treat the move as low-confidence until volume confirms.
- 3
Resolution-risk signal firing
Expires in 0h with open resolution ambiguity.
- 4
Expiry in 0h
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 0 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
- 13:30ResolveHIGH
Market resolves in 0.5h
- 13:02SignalLOW
Signal · Resolution risk
Expires in 0h with open resolution ambiguity.
- 2d agoPriceMEDIUM
Probability up 4.0pp
to 18¢
- 2d agoPriceMEDIUM
Probability up 4.5pp
to 19¢
- 2d agoPriceMEDIUM
Probability up 3.0pp
to 18¢
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Related Markets
14- 18¢-1.0pp
Spread: Eintracht Frankfurt (-1.5)
Other · Vol $0.00
- 8¢-0.5pp
Spread: FC Augsburg (-2.5)
Other · Vol $141.96
- 8¢-0.3pp
Spread: Eintracht Frankfurt (-2.5)
Other · Vol $119.45
- 85¢0.0pp
FC Augsburg vs. Eintracht Frankfurt: O/U 1.5
Other · Vol $316.59
- 65¢+1.5pp
FC Augsburg vs. Eintracht Frankfurt: O/U 2.5
Other · Vol $3.9K
- 43¢+1.5pp
FC Augsburg vs. Eintracht Frankfurt: O/U 3.5
Other · Vol $7.2K
- 23¢0.0pp
FC Augsburg vs. Eintracht Frankfurt: O/U 4.5
Other · Vol $100.73
- 67¢+1.5pp
FC Augsburg vs. Eintracht Frankfurt: Both Teams to Score
Other · Vol $4.4K
- 2¢-2.4pp
Strait of Hormuz traffic returns to normal by end of April?
Other · Vol $2.0M
- 100¢+59.0pp
LoL: Weibo Gaming vs Anyone's Legend - Game 2 Winner
Other · Vol $1.1M
- 59¢-1.0pp
Will FC Barcelona win on 2026-04-25?
Other · Vol $720.5K
- 8¢-30.0pp
Will Aston Villa FC win on 2026-04-25?
Other · Vol $670.7K
- 86¢0.0pp
MegaETH market cap (FDV) >$1B one day after launch?
Other · Vol $568.6K
- 100¢+23.9pp
LoL: T1 vs HANJIN BRION - Game 2 Winner
Other · Vol $541.3K
Market Description
In the upcoming Bundesliga game, scheduled for April 25 at 9:30 AM ET: This market will resolve to "FC Augsburg" if FC Augsburg win the game by 2 or more goals. Otherwise, this market will resolve to "Eintracht Frankfurt". 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 bundesliga.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.bundesliga.com/en/bundesligaNews consensus
- Market type
- Binary
- 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).