Kovalenko Veacheslav vs. Skachenko Serhii

Kovalenko Veacheslav vs. Skachenko Serhii

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

Markets

Kovalenko Veacheslav vs. Skachenko Serhii
Kovalenko Veacheslav vs. Skachenko Serhii
Ended
 
--
Kovalenko Veacheslav vs. Skachenko Serhii: Total Games O/U 3.5
Kovalenko Veacheslav vs. Skachenko Serhii Total Games O/U 3.5
Ended
 
--
Kovalenko Veacheslav vs. Skachenko Serhii: Total Games O/U 4.5
Kovalenko Veacheslav vs. Skachenko Serhii Total Games O/U 4.5
Ended
 
--
Game Handicap: Kovalenko Veacheslav (-1.5) vs Skachenko Serhii (+1.5)
Kovalenko Veacheslav vs. Skachenko Serhii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Skachenko Serhii (-1.5) vs Kovalenko Veacheslav (+1.5)
Kovalenko Veacheslav vs. Skachenko Serhii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kovalenko Veacheslav and Skachenko Serhii in Setka Cup Ukraine Men, scheduled for August 27 at 8:25PM ET. This market will resolve to 'Kovalenko Veacheslav' if Kovalenko Veacheslav wins against Skachenko Serhii. This market will resolve to 'Skachenko Serhii' if Skachenko Serhii wins against Kovalenko Veacheslav. 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 27, 2026 UTC