Will Bosnia and Herzegovina win on 2026-06-12?
Probability
22¢
1h
+0.0pp
24h
+0.0pp
24h Vol
$12.50
Liquidity
$1.1K
Probability (last 7 days)
-1.5pp 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
- 0s agoResolveLOW
Market resolves in 1165.8h
Recent Trades
No recent trades visible from the Data API for this market.
Related Markets
8- 90¢+35.0pp
Spurs vs. Trail Blazers
Other · Vol $7.8M
- 2¢-1.5pp
Strait of Hormuz traffic returns to normal by end of April?
Other · Vol $2.1M
- 0¢-54.4pp
Oilers vs. Ducks
Other · Vol $900.4K
- 0¢-50.4pp
Golden Knights vs. Utah
Other · Vol $755.8K
- 75¢+25.5pp
Spread: Spurs (-2.5)
Other · Vol $707.9K
- 1¢-1.9pp
Starmer out by April 30, 2026?
Other · Vol $431.9K
Market Description
In the upcoming game, scheduled for June 12, 2026 If Bosnia and Herzegovina 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
LOW risk- End date
- Jun 12, 2026
- UMA status
- n/a
- Resolution source
- https://www.fifa.com/fifaplus/en/tournaments/mens/worldcupNews consensus
- Market type
- Multi-outcome (neg-risk)
- Part of a multi-outcome event (neg-risk): only one market can resolve YES.
- Wide spread (6.0¢) — liquidity risk on entry/exit.
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).