Skhabitskiy Sergii vs. Korniichuk Vitalii

Skhabitskiy Sergii vs. Korniichuk Vitalii

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolOct 02, 2026 UTC

Markets

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

Rules

This market refers to the table tennis match between Skhabitskiy Sergii and Korniichuk Vitalii in Setka Cup Ukraine Men, scheduled for September 25 at 7:35AM ET. This market will resolve to 'Skhabitskiy Sergii' if Skhabitskiy Sergii wins against Korniichuk Vitalii. This market will resolve to 'Korniichuk Vitalii' if Korniichuk Vitalii wins against Skhabitskiy Sergii. 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 24, 2026 UTC