Maslovskyi Oleksandr vs. Belanchyk Dmytro

Maslovskyi Oleksandr vs. Belanchyk Dmytro

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

Markets

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

Rules

This market refers to the table tennis match between Maslovskyi Oleksandr and Belanchyk Dmytro in Setka Cup Ukraine Men, scheduled for October 14 at 10:55AM ET. This market will resolve to 'Maslovskyi Oleksandr' if Maslovskyi Oleksandr wins against Belanchyk Dmytro. This market will resolve to 'Belanchyk Dmytro' if Belanchyk Dmytro 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 Oct 13, 2026 UTC