Opryshchenko Yehor vs. Savoliuk Volodymyr

Opryshchenko Yehor vs. Savoliuk Volodymyr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolSep 07, 2026 UTC

Markets

Opryshchenko Yehor vs. Savoliuk Volodymyr
Opryshchenko Yehor vs. Savoliuk Volodymyr
Ended
 
--
Opryshchenko Yehor vs. Savoliuk Volodymyr: Total Games O/U 3.5
Opryshchenko Yehor vs. Savoliuk Volodymyr Total Games O/U 3.5
Ended
 
--
Opryshchenko Yehor vs. Savoliuk Volodymyr: Total Games O/U 4.5
Opryshchenko Yehor vs. Savoliuk Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Opryshchenko Yehor (-1.5) vs Savoliuk Volodymyr (+1.5)
Opryshchenko Yehor vs. Savoliuk Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Savoliuk Volodymyr (-1.5) vs Opryshchenko Yehor (+1.5)
Opryshchenko Yehor vs. Savoliuk Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Opryshchenko Yehor and Savoliuk Volodymyr in Setka Cup Ukraine Men, scheduled for August 31 at 1:30PM ET. This market will resolve to 'Opryshchenko Yehor' if Opryshchenko Yehor wins against Savoliuk Volodymyr. This market will resolve to 'Savoliuk Volodymyr' if Savoliuk Volodymyr wins against Opryshchenko Yehor. 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 30, 2026 UTC