Melnykov Volodymyr vs. Ponomarenko Dmytro

Melnykov Volodymyr vs. Ponomarenko Dmytro

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

Markets

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

Rules

This market refers to the table tennis match between Melnykov Volodymyr and Ponomarenko Dmytro in Setka Cup Ukraine Men, scheduled for October 1 at 4:20AM ET. This market will resolve to 'Melnykov Volodymyr' if Melnykov Volodymyr wins against Ponomarenko Dmytro. This market will resolve to 'Ponomarenko Dmytro' if Ponomarenko Dmytro wins against Melnykov Volodymyr. 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 30, 2026 UTC