Description
No market description is available yet.
Price history
Loading price history...
Market stats
Odds
24h change
7D change
—
30D change
—
24h volume
Total volume
Liquidity
All-time high
—
All-time low
—
Created
Jul 23, 2026, 19:30
Resolve date
Jul 24, 2026, 14:14
Position in event
Odds rank
24h volume rank
24h move rank
Status
Resolved
Parent event
Market Outcomes
Outcome | Odds | Spread | 24h Change | 24h Volume | Total Volume | Liquidity | |
|---|---|---|---|---|---|---|---|
| Danyliuk Nazar vs. Hryban Vadym | — | — | — | — | — | — | |
| Danyliuk Nazar vs. Hryban Vadym Total Games O/U 3.5 | Over | — | — | — | — | — | |
| Danyliuk Nazar vs. Hryban Vadym Total Games O/U 4.5 | Over | — | — | — | — | — | |
| Danyliuk Nazar vs. Hryban Vadym Game Handicap +/-1.5 | Danyliuk Nazar | — | — | — | — | — | |
| Danyliuk Nazar vs. Hryban Vadym Game Handicap +/-1.5 | Hryban Vadym | — | — | — | — | — |
Event Rules
This market refers to the table tennis match between Danyliuk Nazar and Hryban Vadym in Setka Cup Ukraine Men, scheduled for July 24 at 1:55AM ET. This market will resolve to 'Danyliuk Nazar' if Danyliuk Nazar wins against Hryban Vadym. This market will resolve to 'Hryban Vadym' if Hryban Vadym wins against Danyliuk Nazar. If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50. If the match begins but is not completed, and one player advances due to the opponent's retirement, default, or disqualification, this market will resolve to the player who advances. If the match ends in a walkover (player withdraws before the start and the other advances automatically), this market will resolve to 50-50. 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.