Treshchetka Mykola vs. Vasyliev Volodymyr

Treshchetka Mykola vs. Vasyliev Volodymyr

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

Markets

Treshchetka Mykola vs. Vasyliev Volodymyr
Treshchetka Mykola vs. Vasyliev Volodymyr
Ended
 
--
Treshchetka Mykola vs. Vasyliev Volodymyr: Total Games O/U 3.5
Treshchetka Mykola vs. Vasyliev Volodymyr Total Games O/U 3.5
Ended
 
--
Treshchetka Mykola vs. Vasyliev Volodymyr: Total Games O/U 4.5
Treshchetka Mykola vs. Vasyliev Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Treshchetka Mykola (-1.5) vs Vasyliev Volodymyr (+1.5)
Treshchetka Mykola vs. Vasyliev Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Vasyliev Volodymyr (-1.5) vs Treshchetka Mykola (+1.5)
Treshchetka Mykola vs. Vasyliev Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Treshchetka Mykola and Vasyliev Volodymyr in Setka Cup Ukraine Men, scheduled for November 1 at 2:55PM ET. This market will resolve to 'Treshchetka Mykola' if Treshchetka Mykola wins against Vasyliev Volodymyr. This market will resolve to 'Vasyliev Volodymyr' if Vasyliev Volodymyr wins against Treshchetka Mykola. 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 31, 2026 UTC