Potapov Mykhailo vs. Storozhenko Oleksandr

Potapov Mykhailo vs. Storozhenko Oleksandr

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

Markets

Potapov Mykhailo vs. Storozhenko Oleksandr
Potapov Mykhailo vs. Storozhenko Oleksandr
Ended
 
--
Potapov Mykhailo vs. Storozhenko Oleksandr: Total Games O/U 3.5
Potapov Mykhailo vs. Storozhenko Oleksandr Total Games O/U 3.5
Ended
 
--
Potapov Mykhailo vs. Storozhenko Oleksandr: Total Games O/U 4.5
Potapov Mykhailo vs. Storozhenko Oleksandr Total Games O/U 4.5
Ended
 
--
Game Handicap: Potapov Mykhailo (-1.5) vs Storozhenko Oleksandr (+1.5)
Potapov Mykhailo vs. Storozhenko Oleksandr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Storozhenko Oleksandr (-1.5) vs Potapov Mykhailo (+1.5)
Potapov Mykhailo vs. Storozhenko Oleksandr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Potapov Mykhailo and Storozhenko Oleksandr in Setka Cup Ukraine Men, scheduled for August 17 at 5:00PM ET. This market will resolve to 'Potapov Mykhailo' if Potapov Mykhailo wins against Storozhenko Oleksandr. This market will resolve to 'Storozhenko Oleksandr' if Storozhenko Oleksandr wins against Potapov Mykhailo. 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 16, 2026 UTC