Bielskyi Oleksandr vs. Hermakivskyi Illia

Bielskyi Oleksandr vs. Hermakivskyi Illia

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

Markets

Bielskyi Oleksandr vs. Hermakivskyi Illia
Bielskyi Oleksandr vs. Hermakivskyi Illia
Ended
 
--
Bielskyi Oleksandr vs. Hermakivskyi Illia: Total Games O/U 3.5
Bielskyi Oleksandr vs. Hermakivskyi Illia Total Games O/U 3.5
Ended
 
--
Bielskyi Oleksandr vs. Hermakivskyi Illia: Total Games O/U 4.5
Bielskyi Oleksandr vs. Hermakivskyi Illia Total Games O/U 4.5
Ended
 
--
Game Handicap: Bielskyi Oleksandr (-1.5) vs Hermakivskyi Illia (+1.5)
Bielskyi Oleksandr vs. Hermakivskyi Illia Game Handicap +/-1.5
Ended
 
--
Game Handicap: Hermakivskyi Illia (-1.5) vs Bielskyi Oleksandr (+1.5)
Bielskyi Oleksandr vs. Hermakivskyi Illia Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Bielskyi Oleksandr and Hermakivskyi Illia in Setka Cup Ukraine Men, scheduled for September 22 at 12:00PM ET. This market will resolve to 'Bielskyi Oleksandr' if Bielskyi Oleksandr wins against Hermakivskyi Illia. This market will resolve to 'Hermakivskyi Illia' if Hermakivskyi Illia wins against Bielskyi 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 21, 2026 UTC