Tymofeev Oleksandr vs. Voinarovskyi Fedir

Tymofeev Oleksandr vs. Voinarovskyi Fedir

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

Markets

Tymofeev Oleksandr vs. Voinarovskyi Fedir
Tymofeev Oleksandr vs. Voinarovskyi Fedir
Ended
 
--
Tymofeev Oleksandr vs. Voinarovskyi Fedir: Total Games O/U 3.5
Tymofeev Oleksandr vs. Voinarovskyi Fedir Total Games O/U 3.5
Ended
 
--
Tymofeev Oleksandr vs. Voinarovskyi Fedir: Total Games O/U 4.5
Tymofeev Oleksandr vs. Voinarovskyi Fedir Total Games O/U 4.5
Ended
 
--
Game Handicap: Tymofeev Oleksandr (-1.5) vs Voinarovskyi Fedir (+1.5)
Tymofeev Oleksandr vs. Voinarovskyi Fedir Game Handicap +/-1.5
Ended
 
--
Game Handicap: Voinarovskyi Fedir (-1.5) vs Tymofeev Oleksandr (+1.5)
Tymofeev Oleksandr vs. Voinarovskyi Fedir Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Tymofeev Oleksandr and Voinarovskyi Fedir in Setka Cup Ukraine Men, scheduled for September 5 at 10:00AM ET. This market will resolve to 'Tymofeev Oleksandr' if Tymofeev Oleksandr wins against Voinarovskyi Fedir. This market will resolve to 'Voinarovskyi Fedir' if Voinarovskyi Fedir wins against Tymofeev 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 Sep 04, 2026 UTC