Kolesnykov Valerii vs. Bilobrov Volodymyr

Kolesnykov Valerii vs. Bilobrov Volodymyr

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

Markets

Kolesnykov Valerii vs. Bilobrov Volodymyr
Kolesnykov Valerii vs. Bilobrov Volodymyr
Ended
 
--
Kolesnykov Valerii vs. Bilobrov Volodymyr: Total Games O/U 3.5
Kolesnykov Valerii vs. Bilobrov Volodymyr Total Games O/U 3.5
Ended
 
--
Kolesnykov Valerii vs. Bilobrov Volodymyr: Total Games O/U 4.5
Kolesnykov Valerii vs. Bilobrov Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Kolesnykov Valerii (-1.5) vs Bilobrov Volodymyr (+1.5)
Kolesnykov Valerii vs. Bilobrov Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Bilobrov Volodymyr (-1.5) vs Kolesnykov Valerii (+1.5)
Kolesnykov Valerii vs. Bilobrov Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kolesnykov Valerii and Bilobrov Volodymyr in Setka Cup Ukraine Men, scheduled for September 21 at 3:00AM ET. This market will resolve to 'Kolesnykov Valerii' if Kolesnykov Valerii wins against Bilobrov Volodymyr. This market will resolve to 'Bilobrov Volodymyr' if Bilobrov Volodymyr wins against Kolesnykov Valerii. 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 20, 2026 UTC