Lytvyn Vsevolod vs. Strutinskiy Oleksandr

Lytvyn Vsevolod vs. Strutinskiy Oleksandr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolNov 09, 2026 UTC

Markets

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

Rules

This market refers to the table tennis match between Lytvyn Vsevolod and Strutinskiy Oleksandr in Setka Cup Ukraine Men, scheduled for November 2 at 8:10AM ET. This market will resolve to 'Lytvyn Vsevolod' if Lytvyn Vsevolod wins against Strutinskiy Oleksandr. This market will resolve to 'Strutinskiy Oleksandr' if Strutinskiy Oleksandr wins against Lytvyn Vsevolod. 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 Nov 01, 2026 UTC