Populovskyi Eduard vs. Ovsiienko Oleksandr

Populovskyi Eduard vs. Ovsiienko Oleksandr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolAug 31, 2026 UTC

Markets

Populovskyi Eduard vs. Ovsiienko Oleksandr
Populovskyi Eduard vs. Ovsiienko Oleksandr
Ended
 
--
Populovskyi Eduard vs. Ovsiienko Oleksandr: Total Games O/U 3.5
Populovskyi Eduard vs. Ovsiienko Oleksandr Total Games O/U 3.5
Ended
 
--
Populovskyi Eduard vs. Ovsiienko Oleksandr: Total Games O/U 4.5
Populovskyi Eduard vs. Ovsiienko Oleksandr Total Games O/U 4.5
Ended
 
--
Game Handicap: Populovskyi Eduard (-1.5) vs Ovsiienko Oleksandr (+1.5)
Populovskyi Eduard vs. Ovsiienko Oleksandr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Ovsiienko Oleksandr (-1.5) vs Populovskyi Eduard (+1.5)
Populovskyi Eduard vs. Ovsiienko Oleksandr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Populovskyi Eduard and Ovsiienko Oleksandr in Setka Cup Ukraine Men, scheduled for August 24 at 1:50AM ET. This market will resolve to 'Populovskyi Eduard' if Populovskyi Eduard wins against Ovsiienko Oleksandr. This market will resolve to 'Ovsiienko Oleksandr' if Ovsiienko Oleksandr wins against Populovskyi Eduard. 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 23, 2026 UTC