Maksiuta Volodymyr vs. Opryshchenko Yehor

Maksiuta Volodymyr vs. Opryshchenko Yehor

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolSep 10, 2026 UTC

Markets

Maksiuta Volodymyr vs. Opryshchenko Yehor
Maksiuta Volodymyr vs. Opryshchenko Yehor
Ended
 
--
Maksiuta Volodymyr vs. Opryshchenko Yehor: Total Games O/U 3.5
Maksiuta Volodymyr vs. Opryshchenko Yehor Total Games O/U 3.5
Ended
 
--
Maksiuta Volodymyr vs. Opryshchenko Yehor: Total Games O/U 4.5
Maksiuta Volodymyr vs. Opryshchenko Yehor Total Games O/U 4.5
Ended
 
--
Game Handicap: Maksiuta Volodymyr (-1.5) vs Opryshchenko Yehor (+1.5)
Maksiuta Volodymyr vs. Opryshchenko Yehor Game Handicap +/-1.5
Ended
 
--
Game Handicap: Opryshchenko Yehor (-1.5) vs Maksiuta Volodymyr (+1.5)
Maksiuta Volodymyr vs. Opryshchenko Yehor Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Maksiuta Volodymyr and Opryshchenko Yehor in Setka Cup Ukraine Men, scheduled for September 3 at 9:30AM ET. This market will resolve to 'Maksiuta Volodymyr' if Maksiuta Volodymyr wins against Opryshchenko Yehor. This market will resolve to 'Opryshchenko Yehor' if Opryshchenko Yehor wins against Maksiuta Volodymyr. 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 02, 2026 UTC