Skorobahatyi Yevhen vs. Strutinskiy Oleksandr

Skorobahatyi Yevhen vs. Strutinskiy Oleksandr

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

Markets

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

Rules

This market refers to the table tennis match between Skorobahatyi Yevhen and Strutinskiy Oleksandr in Setka Cup Ukraine Men, scheduled for September 4 at 8:20AM ET. This market will resolve to 'Skorobahatyi Yevhen' if Skorobahatyi Yevhen wins against Strutinskiy Oleksandr. This market will resolve to 'Strutinskiy Oleksandr' if Strutinskiy Oleksandr wins against Skorobahatyi Yevhen. 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 03, 2026 UTC