Klymenko Kostiantyn vs. Kovalenko Anatolii

Klymenko Kostiantyn vs. Kovalenko Anatolii

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

Markets

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

Rules

This market refers to the table tennis match between Klymenko Kostiantyn and Kovalenko Anatolii in Setka Cup Ukraine Men, scheduled for September 4 at 6:05AM ET. This market will resolve to 'Klymenko Kostiantyn' if Klymenko Kostiantyn wins against Kovalenko Anatolii. This market will resolve to 'Kovalenko Anatolii' if Kovalenko Anatolii 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 Sep 03, 2026 UTC