Storozhenko Oleksandr vs. Parahailo Yurii

Storozhenko Oleksandr vs. Parahailo Yurii

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

Markets

Storozhenko Oleksandr vs. Parahailo Yurii
Storozhenko Oleksandr vs. Parahailo Yurii
Ended
 
--
Storozhenko Oleksandr vs. Parahailo Yurii: Total Games O/U 3.5
Storozhenko Oleksandr vs. Parahailo Yurii Total Games O/U 3.5
Ended
 
--
Storozhenko Oleksandr vs. Parahailo Yurii: Total Games O/U 4.5
Storozhenko Oleksandr vs. Parahailo Yurii Total Games O/U 4.5
Ended
 
--
Game Handicap: Storozhenko Oleksandr (-1.5) vs Parahailo Yurii (+1.5)
Storozhenko Oleksandr vs. Parahailo Yurii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Parahailo Yurii (-1.5) vs Storozhenko Oleksandr (+1.5)
Storozhenko Oleksandr vs. Parahailo Yurii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Storozhenko Oleksandr and Parahailo Yurii in Setka Cup Ukraine Men, scheduled for October 22 at 4:15PM ET. This market will resolve to 'Storozhenko Oleksandr' if Storozhenko Oleksandr wins against Parahailo Yurii. This market will resolve to 'Parahailo Yurii' if Parahailo Yurii wins against Storozhenko 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 Oct 21, 2026 UTC