Voronenkov Volodymyr vs. Riadynskyi Yehor

Voronenkov Volodymyr vs. Riadynskyi Yehor

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

Markets

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

Rules

This market refers to the table tennis match between Voronenkov Volodymyr and Riadynskyi Yehor in Setka Cup Ukraine Men, scheduled for October 16 at 10:30AM ET. This market will resolve to 'Voronenkov Volodymyr' if Voronenkov Volodymyr wins against Riadynskyi Yehor. This market will resolve to 'Riadynskyi Yehor' if Riadynskyi Yehor wins against Voronenkov 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 Oct 15, 2026 UTC