Voinarovskyi Fedir vs. Tymofeev Oleksandr

Voinarovskyi Fedir vs. Tymofeev Oleksandr

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

Markets

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

Rules

This market refers to the table tennis match between Voinarovskyi Fedir and Tymofeev Oleksandr in Setka Cup Ukraine Men, scheduled for August 29 at 1:00PM ET. This market will resolve to 'Voinarovskyi Fedir' if Voinarovskyi Fedir wins against Tymofeev Oleksandr. This market will resolve to 'Tymofeev Oleksandr' if Tymofeev Oleksandr wins against Voinarovskyi Fedir. 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 28, 2026 UTC