Skhabitskiy Sergii vs. Melnykov Volodymyr

Skhabitskiy Sergii vs. Melnykov Volodymyr

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

Markets

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

Rules

This market refers to the table tennis match between Skhabitskiy Sergii and Melnykov Volodymyr in Setka Cup Ukraine Men, scheduled for October 14 at 8:00AM ET. This market will resolve to 'Skhabitskiy Sergii' if Skhabitskiy Sergii wins against Melnykov Volodymyr. This market will resolve to 'Melnykov Volodymyr' if Melnykov Volodymyr 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 Oct 13, 2026 UTC