Kaidakov Volodymyr vs. Vorsulyak Yaroslav

Kaidakov Volodymyr vs. Vorsulyak Yaroslav

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

Markets

Kaidakov Volodymyr vs. Vorsulyak Yaroslav
Kaidakov Volodymyr vs. Vorsulyak Yaroslav
Ended
 
--
Kaidakov Volodymyr vs. Vorsulyak Yaroslav: Total Games O/U 3.5
Kaidakov Volodymyr vs. Vorsulyak Yaroslav Total Games O/U 3.5
Ended
 
--
Kaidakov Volodymyr vs. Vorsulyak Yaroslav: Total Games O/U 4.5
Kaidakov Volodymyr vs. Vorsulyak Yaroslav Total Games O/U 4.5
Ended
 
--
Game Handicap: Kaidakov Volodymyr (-1.5) vs Vorsulyak Yaroslav (+1.5)
Kaidakov Volodymyr vs. Vorsulyak Yaroslav Game Handicap +/-1.5
Ended
 
--
Game Handicap: Vorsulyak Yaroslav (-1.5) vs Kaidakov Volodymyr (+1.5)
Kaidakov Volodymyr vs. Vorsulyak Yaroslav Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kaidakov Volodymyr and Vorsulyak Yaroslav in Setka Cup Ukraine Men, scheduled for October 5 at 7:45PM ET. This market will resolve to 'Kaidakov Volodymyr' if Kaidakov Volodymyr wins against Vorsulyak Yaroslav. This market will resolve to 'Vorsulyak Yaroslav' if Vorsulyak Yaroslav wins against Kaidakov 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 04, 2026 UTC