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 22, 2026, 23:30
Resolve date
Jul 24, 2026, 14:04
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 | |
|---|---|---|---|---|---|---|---|
| Regush Andrii vs. Slozka Viktor | — | — | — | — | — | — | |
| Regush Andrii vs. Slozka Viktor Total Games O/U 3.5 | Over | — | — | — | — | — | |
| Regush Andrii vs. Slozka Viktor Total Games O/U 4.5 | Over | — | — | — | — | — | |
| Regush Andrii vs. Slozka Viktor Game Handicap +/-1.5 | Regush Andrii | — | — | — | — | — | |
| Regush Andrii vs. Slozka Viktor Game Handicap +/-1.5 | Slozka Viktor | — | — | — | — | — |
Event Rules
This market refers to the table tennis match between Regush Andrii and Slozka Viktor in Setka Cup Ukraine Men, scheduled for July 23 at 1:05PM ET. This market will resolve to 'Regush Andrii' if Regush Andrii wins against Slozka Viktor. This market will resolve to 'Slozka Viktor' if Slozka Viktor wins against Regush Andrii. 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.