Sokoltsov Yevhenii vs. Khandetskyi Serhii

Sokoltsov Yevhenii vs. Khandetskyi Serhii

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

Markets

Sokoltsov Yevhenii vs. Khandetskyi Serhii
Sokoltsov Yevhenii vs. Khandetskyi Serhii
Ended
 
--
Sokoltsov Yevhenii vs. Khandetskyi Serhii: Total Games O/U 3.5
Sokoltsov Yevhenii vs. Khandetskyi Serhii Total Games O/U 3.5
Ended
 
--
Sokoltsov Yevhenii vs. Khandetskyi Serhii: Total Games O/U 4.5
Sokoltsov Yevhenii vs. Khandetskyi Serhii Total Games O/U 4.5
Ended
 
--
Game Handicap: Sokoltsov Yevhenii (-1.5) vs Khandetskyi Serhii (+1.5)
Sokoltsov Yevhenii vs. Khandetskyi Serhii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Khandetskyi Serhii (-1.5) vs Sokoltsov Yevhenii (+1.5)
Sokoltsov Yevhenii vs. Khandetskyi Serhii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Sokoltsov Yevhenii and Khandetskyi Serhii in Setka Cup Ukraine Men, scheduled for September 15 at 12:55PM ET. This market will resolve to 'Sokoltsov Yevhenii' if Sokoltsov Yevhenii wins against Khandetskyi Serhii. This market will resolve to 'Khandetskyi Serhii' if Khandetskyi Serhii wins against Sokoltsov Yevhenii. 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 14, 2026 UTC