Khandetskyi Serhii vs. Sokoltsov Yevhenii

Khandetskyi Serhii vs. Sokoltsov Yevhenii

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

Markets

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

Rules

This market refers to the table tennis match between Khandetskyi Serhii and Sokoltsov Yevhenii in Setka Cup Ukraine Men, scheduled for November 3 at 11:35PM ET. This market will resolve to 'Khandetskyi Serhii' if Khandetskyi Serhii wins against Sokoltsov Yevhenii. This market will resolve to 'Sokoltsov Yevhenii' if Sokoltsov Yevhenii wins against Khandetskyi Serhii. 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 Nov 03, 2026 UTC