Melnykov Volodymyr vs. Tymofeev Oleksandr

Melnykov Volodymyr vs. Tymofeev Oleksandr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolAug 23, 2026 UTC

Markets

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

Rules

This market refers to the table tennis match between Melnykov Volodymyr and Tymofeev Oleksandr in Setka Cup Ukraine Men, scheduled for August 16 at 4:20AM ET. This market will resolve to 'Melnykov Volodymyr' if Melnykov Volodymyr wins against Tymofeev Oleksandr. This market will resolve to 'Tymofeev Oleksandr' if Tymofeev Oleksandr 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 Aug 15, 2026 UTC