Kryvorotko Yevhen vs. Kovalchuk Oleksandr

Kryvorotko Yevhen vs. Kovalchuk Oleksandr

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

Markets

Kryvorotko Yevhen vs. Kovalchuk Oleksandr
Kryvorotko Yevhen vs. Kovalchuk Oleksandr
Ended
 
--
Kryvorotko Yevhen vs. Kovalchuk Oleksandr: Total Games O/U 3.5
Kryvorotko Yevhen vs. Kovalchuk Oleksandr Total Games O/U 3.5
Ended
 
--
Kryvorotko Yevhen vs. Kovalchuk Oleksandr: Total Games O/U 4.5
Kryvorotko Yevhen vs. Kovalchuk Oleksandr Total Games O/U 4.5
Ended
 
--
Game Handicap: Kryvorotko Yevhen (-1.5) vs Kovalchuk Oleksandr (+1.5)
Kryvorotko Yevhen vs. Kovalchuk Oleksandr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Kovalchuk Oleksandr (-1.5) vs Kryvorotko Yevhen (+1.5)
Kryvorotko Yevhen vs. Kovalchuk Oleksandr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kryvorotko Yevhen and Kovalchuk Oleksandr in Setka Cup Ukraine Men, scheduled for October 3 at 7:25PM ET. This market will resolve to 'Kryvorotko Yevhen' if Kryvorotko Yevhen wins against Kovalchuk Oleksandr. This market will resolve to 'Kovalchuk Oleksandr' if Kovalchuk Oleksandr wins against Kryvorotko Yevhen. 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 02, 2026 UTC