Treshchetka Mykola vs. Vivatenko Mykhailo

Treshchetka Mykola vs. Vivatenko Mykhailo

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

Markets

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

Rules

This market refers to the table tennis match between Treshchetka Mykola and Vivatenko Mykhailo in Setka Cup Ukraine Men, scheduled for September 25 at 5:25AM ET. This market will resolve to 'Treshchetka Mykola' if Treshchetka Mykola wins against Vivatenko Mykhailo. This market will resolve to 'Vivatenko Mykhailo' if Vivatenko Mykhailo 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 Sep 24, 2026 UTC