Varchenko Volodymyr vs. Hovorunets Serhii

Varchenko Volodymyr vs. Hovorunets Serhii

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

Markets

Varchenko Volodymyr vs. Hovorunets Serhii
Varchenko Volodymyr vs. Hovorunets Serhii
Ended
 
--
Varchenko Volodymyr vs. Hovorunets Serhii: Total Games O/U 3.5
Varchenko Volodymyr vs. Hovorunets Serhii Total Games O/U 3.5
Ended
 
--
Varchenko Volodymyr vs. Hovorunets Serhii: Total Games O/U 4.5
Varchenko Volodymyr vs. Hovorunets Serhii Total Games O/U 4.5
Ended
 
--
Game Handicap: Varchenko Volodymyr (-1.5) vs Hovorunets Serhii (+1.5)
Varchenko Volodymyr vs. Hovorunets Serhii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Hovorunets Serhii (-1.5) vs Varchenko Volodymyr (+1.5)
Varchenko Volodymyr vs. Hovorunets Serhii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Varchenko Volodymyr and Hovorunets Serhii in Setka Cup Ukraine Men, scheduled for September 22 at 7:40AM ET. This market will resolve to 'Varchenko Volodymyr' if Varchenko Volodymyr wins against Hovorunets Serhii. This market will resolve to 'Hovorunets Serhii' if Hovorunets Serhii wins against Varchenko Volodymyr. 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 Sep 21, 2026 UTC