Kovalchuk Vladyslav vs. Korobko Volodymyr

Kovalchuk Vladyslav vs. Korobko Volodymyr

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

Markets

Kovalchuk Vladyslav vs. Korobko Volodymyr
Kovalchuk Vladyslav vs. Korobko Volodymyr
Ended
 
--
Kovalchuk Vladyslav vs. Korobko Volodymyr: Total Games O/U 3.5
Kovalchuk Vladyslav vs. Korobko Volodymyr Total Games O/U 3.5
Ended
 
--
Kovalchuk Vladyslav vs. Korobko Volodymyr: Total Games O/U 4.5
Kovalchuk Vladyslav vs. Korobko Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Kovalchuk Vladyslav (-1.5) vs Korobko Volodymyr (+1.5)
Kovalchuk Vladyslav vs. Korobko Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Korobko Volodymyr (-1.5) vs Kovalchuk Vladyslav (+1.5)
Kovalchuk Vladyslav vs. Korobko Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kovalchuk Vladyslav and Korobko Volodymyr in Setka Cup Ukraine Men, scheduled for October 21 at 7:15PM ET. This market will resolve to 'Kovalchuk Vladyslav' if Kovalchuk Vladyslav wins against Korobko Volodymyr. This market will resolve to 'Korobko Volodymyr' if Korobko Volodymyr wins against Kovalchuk Vladyslav. 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