Leymanovsky Yurii vs. Chornobab Volodymyr

Leymanovsky Yurii vs. Chornobab Volodymyr

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

Markets

Leymanovsky Yurii vs. Chornobab Volodymyr
Leymanovsky Yurii vs. Chornobab Volodymyr
Ended
 
--
Leymanovsky Yurii vs. Chornobab Volodymyr: Total Games O/U 3.5
Leymanovsky Yurii vs. Chornobab Volodymyr Total Games O/U 3.5
Ended
 
--
Leymanovsky Yurii vs. Chornobab Volodymyr: Total Games O/U 4.5
Leymanovsky Yurii vs. Chornobab Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Leymanovsky Yurii (-1.5) vs Chornobab Volodymyr (+1.5)
Leymanovsky Yurii vs. Chornobab Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Chornobab Volodymyr (-1.5) vs Leymanovsky Yurii (+1.5)
Leymanovsky Yurii vs. Chornobab Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Leymanovsky Yurii and Chornobab Volodymyr in Setka Cup Ukraine Men, scheduled for August 19 at 7:50AM ET. This market will resolve to 'Leymanovsky Yurii' if Leymanovsky Yurii wins against Chornobab Volodymyr. This market will resolve to 'Chornobab Volodymyr' if Chornobab Volodymyr wins against Leymanovsky Yurii. 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 18, 2026 UTC