Maslovskyi Oleksandr vs. Salivonchyk Vasyl

Maslovskyi Oleksandr vs. Salivonchyk Vasyl

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

Markets

Maslovskyi Oleksandr vs. Salivonchyk Vasyl
Maslovskyi Oleksandr vs. Salivonchyk Vasyl
Ended
 
--
Maslovskyi Oleksandr vs. Salivonchyk Vasyl: Total Games O/U 3.5
Maslovskyi Oleksandr vs. Salivonchyk Vasyl Total Games O/U 3.5
Ended
 
--
Maslovskyi Oleksandr vs. Salivonchyk Vasyl: Total Games O/U 4.5
Maslovskyi Oleksandr vs. Salivonchyk Vasyl Total Games O/U 4.5
Ended
 
--
Game Handicap: Maslovskyi Oleksandr (-1.5) vs Salivonchyk Vasyl (+1.5)
Maslovskyi Oleksandr vs. Salivonchyk Vasyl Game Handicap +/-1.5
Ended
 
--
Game Handicap: Salivonchyk Vasyl (-1.5) vs Maslovskyi Oleksandr (+1.5)
Maslovskyi Oleksandr vs. Salivonchyk Vasyl Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Maslovskyi Oleksandr and Salivonchyk Vasyl in Setka Cup Ukraine Men, scheduled for August 16 at 9:25AM ET. This market will resolve to 'Maslovskyi Oleksandr' if Maslovskyi Oleksandr wins against Salivonchyk Vasyl. This market will resolve to 'Salivonchyk Vasyl' if Salivonchyk Vasyl wins against Maslovskyi Oleksandr. 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