Dukhovenko Oleksandr vs. Pysmennyi Yevhen

Dukhovenko Oleksandr vs. Pysmennyi Yevhen

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

Markets

Dukhovenko Oleksandr vs. Pysmennyi Yevhen
Dukhovenko Oleksandr vs. Pysmennyi Yevhen
Ended
 
--
Dukhovenko Oleksandr vs. Pysmennyi Yevhen: Total Games O/U 3.5
Dukhovenko Oleksandr vs. Pysmennyi Yevhen Total Games O/U 3.5
Ended
 
--
Dukhovenko Oleksandr vs. Pysmennyi Yevhen: Total Games O/U 4.5
Dukhovenko Oleksandr vs. Pysmennyi Yevhen Total Games O/U 4.5
Ended
 
--
Game Handicap: Dukhovenko Oleksandr (-1.5) vs Pysmennyi Yevhen (+1.5)
Dukhovenko Oleksandr vs. Pysmennyi Yevhen Game Handicap +/-1.5
Ended
 
--
Game Handicap: Pysmennyi Yevhen (-1.5) vs Dukhovenko Oleksandr (+1.5)
Dukhovenko Oleksandr vs. Pysmennyi Yevhen Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Dukhovenko Oleksandr and Pysmennyi Yevhen in Setka Cup Ukraine Men, scheduled for October 17 at 10:55AM ET. This market will resolve to 'Dukhovenko Oleksandr' if Dukhovenko Oleksandr wins against Pysmennyi Yevhen. This market will resolve to 'Pysmennyi Yevhen' if Pysmennyi Yevhen wins against Dukhovenko 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 16, 2026 UTC