Fedoryshyn Ivan vs. Seliuchenko Oleksandr

Fedoryshyn Ivan vs. Seliuchenko Oleksandr

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

Markets

Fedoryshyn Ivan vs. Seliuchenko Oleksandr
Fedoryshyn Ivan vs. Seliuchenko Oleksandr
Ended
 
--
Fedoryshyn Ivan vs. Seliuchenko Oleksandr: Total Games O/U 3.5
Fedoryshyn Ivan vs. Seliuchenko Oleksandr Total Games O/U 3.5
Ended
 
--
Fedoryshyn Ivan vs. Seliuchenko Oleksandr: Total Games O/U 4.5
Fedoryshyn Ivan vs. Seliuchenko Oleksandr Total Games O/U 4.5
Ended
 
--
Game Handicap: Fedoryshyn Ivan (-1.5) vs Seliuchenko Oleksandr (+1.5)
Fedoryshyn Ivan vs. Seliuchenko Oleksandr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Seliuchenko Oleksandr (-1.5) vs Fedoryshyn Ivan (+1.5)
Fedoryshyn Ivan vs. Seliuchenko Oleksandr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Fedoryshyn Ivan and Seliuchenko Oleksandr in Setka Cup Ukraine Men, scheduled for September 21 at 11:10AM ET. This market will resolve to 'Fedoryshyn Ivan' if Fedoryshyn Ivan wins against Seliuchenko Oleksandr. This market will resolve to 'Seliuchenko Oleksandr' if Seliuchenko Oleksandr wins against Fedoryshyn Ivan. 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 20, 2026 UTC