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 27, 2026, 21:33
Resolve date
Jul 28, 2026, 09:12
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 | |
|---|---|---|---|---|---|---|---|
| Balabei Serhii vs. Kushnirenko Serhii | Balabei Serhii | — | — | — | — | — | |
| Balabei Serhii vs. Kushnirenko Serhii Total Games O/U 3.5 | Under | — | — | — | — | — | |
| Balabei Serhii vs. Kushnirenko Serhii Total Games O/U 4.5 | Under | — | — | — | — | — | |
| Balabei Serhii vs. Kushnirenko Serhii Game Handicap +/-1.5 | Balabei Serhii | — | — | — | — | — | |
| Balabei Serhii vs. Kushnirenko Serhii Game Handicap +/-1.5 | Balabei Serhii | — | — | — | — | — |
Event Rules
This market refers to the table tennis match between Balabei Serhii and Kushnirenko Serhii in Setka Cup Ukraine Men, scheduled for July 28 at 4:30AM ET. This market will resolve to 'Balabei Serhii' if Balabei Serhii wins against Kushnirenko Serhii. This market will resolve to 'Kushnirenko Serhii' if Kushnirenko Serhii wins against Balabei Serhii. 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.