Klymenko Kostiantyn vs. Skhabitskiy Sergii

Klymenko Kostiantyn vs. Skhabitskiy Sergii

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolAug 24, 2026 UTC

Markets

Klymenko Kostiantyn vs. Skhabitskiy Sergii
Klymenko Kostiantyn vs. Skhabitskiy Sergii
Ended
 
--
Klymenko Kostiantyn vs. Skhabitskiy Sergii: Total Games O/U 3.5
Klymenko Kostiantyn vs. Skhabitskiy Sergii Total Games O/U 3.5
Ended
 
--
Klymenko Kostiantyn vs. Skhabitskiy Sergii: Total Games O/U 4.5
Klymenko Kostiantyn vs. Skhabitskiy Sergii Total Games O/U 4.5
Ended
 
--
Game Handicap: Klymenko Kostiantyn (-1.5) vs Skhabitskiy Sergii (+1.5)
Klymenko Kostiantyn vs. Skhabitskiy Sergii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Skhabitskiy Sergii (-1.5) vs Klymenko Kostiantyn (+1.5)
Klymenko Kostiantyn vs. Skhabitskiy Sergii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Klymenko Kostiantyn and Skhabitskiy Sergii in Setka Cup Ukraine Men, scheduled for August 17 at 3:20AM ET. This market will resolve to 'Klymenko Kostiantyn' if Klymenko Kostiantyn wins against Skhabitskiy Sergii. This market will resolve to 'Skhabitskiy Sergii' if Skhabitskiy Sergii wins against Klymenko Kostiantyn. 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 16, 2026 UTC