Shchegelskyi Dmytro vs. Pohonov Oleksandr

Shchegelskyi Dmytro vs. Pohonov Oleksandr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolAug 27, 2026 UTC

Markets

Shchegelskyi Dmytro vs. Pohonov Oleksandr
Shchegelskyi Dmytro vs. Pohonov Oleksandr
Ended
 
--
Shchegelskyi Dmytro vs. Pohonov Oleksandr: Total Games O/U 3.5
Shchegelskyi Dmytro vs. Pohonov Oleksandr Total Games O/U 3.5
Ended
 
--
Shchegelskyi Dmytro vs. Pohonov Oleksandr: Total Games O/U 4.5
Shchegelskyi Dmytro vs. Pohonov Oleksandr Total Games O/U 4.5
Ended
 
--
Game Handicap: Shchegelskyi Dmytro (-1.5) vs Pohonov Oleksandr (+1.5)
Shchegelskyi Dmytro vs. Pohonov Oleksandr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Pohonov Oleksandr (-1.5) vs Shchegelskyi Dmytro (+1.5)
Shchegelskyi Dmytro vs. Pohonov Oleksandr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Shchegelskyi Dmytro and Pohonov Oleksandr in Setka Cup Ukraine Men, scheduled for August 20 at 10:05AM ET. This market will resolve to 'Shchegelskyi Dmytro' if Shchegelskyi Dmytro wins against Pohonov Oleksandr. This market will resolve to 'Pohonov Oleksandr' if Pohonov Oleksandr wins against Shchegelskyi Dmytro. 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.

Created Aug 19, 2026 UTC