Voronenkov Volodymyr vs. Levshyn Anatolii

Voronenkov Volodymyr vs. Levshyn Anatolii

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolOct 15, 2026 UTC

Markets

Voronenkov Volodymyr vs. Levshyn Anatolii
Voronenkov Volodymyr vs. Levshyn Anatolii
Ended
 
--
Voronenkov Volodymyr vs. Levshyn Anatolii: Total Games O/U 3.5
Voronenkov Volodymyr vs. Levshyn Anatolii Total Games O/U 3.5
Ended
 
--
Voronenkov Volodymyr vs. Levshyn Anatolii: Total Games O/U 4.5
Voronenkov Volodymyr vs. Levshyn Anatolii Total Games O/U 4.5
Ended
 
--
Game Handicap: Voronenkov Volodymyr (-1.5) vs Levshyn Anatolii (+1.5)
Voronenkov Volodymyr vs. Levshyn Anatolii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Levshyn Anatolii (-1.5) vs Voronenkov Volodymyr (+1.5)
Voronenkov Volodymyr vs. Levshyn Anatolii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Voronenkov Volodymyr and Levshyn Anatolii in Setka Cup Ukraine Men, scheduled for October 8 at 9:30AM ET. This market will resolve to 'Voronenkov Volodymyr' if Voronenkov Volodymyr wins against Levshyn Anatolii. This market will resolve to 'Levshyn Anatolii' if Levshyn Anatolii wins against Voronenkov 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 Oct 07, 2026 UTC