Bilobrov Volodymyr vs. Kovalenko Anatolii

Bilobrov Volodymyr vs. Kovalenko Anatolii

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

Markets

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

Rules

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