Strutinskiy Oleksandr vs. Riadynskyi Yehor

Strutinskiy Oleksandr vs. Riadynskyi Yehor

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

Markets

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

Rules

This market refers to the table tennis match between Strutinskiy Oleksandr and Riadynskyi Yehor in Setka Cup Ukraine Men, scheduled for August 17 at 1:30PM ET. This market will resolve to 'Strutinskiy Oleksandr' if Strutinskiy Oleksandr wins against Riadynskyi Yehor. This market will resolve to 'Riadynskyi Yehor' if Riadynskyi Yehor wins against Strutinskiy 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 16, 2026 UTC