Yavorskiy Oleksandr vs. Melintii Vladimir

Yavorskiy Oleksandr vs. Melintii Vladimir

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Moldova MenSportsTable Tennis
$0 Total VolSep 17, 2026 UTC

Markets

Yavorskiy Oleksandr vs. Melintii Vladimir
Yavorskiy Oleksandr vs. Melintii Vladimir
Ended
 
--
Yavorskiy Oleksandr vs. Melintii Vladimir: Total Games O/U 3.5
Yavorskiy Oleksandr vs. Melintii Vladimir Total Games O/U 3.5
Ended
 
--
Yavorskiy Oleksandr vs. Melintii Vladimir: Total Games O/U 4.5
Yavorskiy Oleksandr vs. Melintii Vladimir Total Games O/U 4.5
Ended
 
--
Game Handicap: Yavorskiy Oleksandr (-1.5) vs Melintii Vladimir (+1.5)
Yavorskiy Oleksandr vs. Melintii Vladimir Game Handicap +/-1.5
Ended
 
--
Game Handicap: Melintii Vladimir (-1.5) vs Yavorskiy Oleksandr (+1.5)
Yavorskiy Oleksandr vs. Melintii Vladimir Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Yavorskiy Oleksandr and Melintii Vladimir in Setka Cup Moldova Men, scheduled for September 10 at 4:45PM ET. This market will resolve to 'Yavorskiy Oleksandr' if Yavorskiy Oleksandr wins against Melintii Vladimir. This market will resolve to 'Melintii Vladimir' if Melintii Vladimir wins against Yavorskiy 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 Sep 09, 2026 UTC