Description
No market description is available yet.
Price history
Price history is unavailable because this market does not expose a primary chart outcome yet.
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:15
Resolve date
Aug 4, 2026, 13:25
Position in event
Odds rank
24h volume rank
24h move rank
Status
Active
Parent event
Market Outcomes
Outcome | Odds | Spread | 24h Change | 24h Volume | Total Volume | Liquidity | |
|---|---|---|---|---|---|---|---|
| Elfemov Ivan vs. Sydorenko Vitalii | — | — | — | — | — | — | |
| Elfemov Ivan vs. Sydorenko Vitalii Total Games O/U 3.5 | — | — | — | — | — | — | |
| Elfemov Ivan vs. Sydorenko Vitalii Total Games O/U 4.5 | — | — | — | — | — | — | |
| Elfemov Ivan vs. Sydorenko Vitalii Game Handicap +/-1.5 | — | — | — | — | — | — | |
| Elfemov Ivan vs. Sydorenko Vitalii Game Handicap +/-1.5 | — | — | — | — | — | — |
Event Rules
This market refers to the table tennis match between Elfemov Ivan and Sydorenko Vitalii in Setka Cup Ukraine Men, scheduled for July 28 at 9:25AM ET. This market will resolve to 'Elfemov Ivan' if Elfemov Ivan wins against Sydorenko Vitalii. This market will resolve to 'Sydorenko Vitalii' if Sydorenko Vitalii wins against Elfemov Ivan. 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.