Habrelyan Daniil vs. Nadporozhskyi Oleksii

Habrelyan Daniil vs. Nadporozhskyi Oleksii

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

Markets

Habrelyan Daniil vs. Nadporozhskyi Oleksii
Habrelyan Daniil vs. Nadporozhskyi Oleksii
Ended
 
--
Habrelyan Daniil vs. Nadporozhskyi Oleksii: Total Games O/U 3.5
Habrelyan Daniil vs. Nadporozhskyi Oleksii Total Games O/U 3.5
Ended
 
--
Habrelyan Daniil vs. Nadporozhskyi Oleksii: Total Games O/U 4.5
Habrelyan Daniil vs. Nadporozhskyi Oleksii Total Games O/U 4.5
Ended
 
--
Game Handicap: Habrelyan Daniil (-1.5) vs Nadporozhskyi Oleksii (+1.5)
Habrelyan Daniil vs. Nadporozhskyi Oleksii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Nadporozhskyi Oleksii (-1.5) vs Habrelyan Daniil (+1.5)
Habrelyan Daniil vs. Nadporozhskyi Oleksii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Habrelyan Daniil and Nadporozhskyi Oleksii in Setka Cup Ukraine Men, scheduled for September 9 at 1:10PM ET. This market will resolve to 'Habrelyan Daniil' if Habrelyan Daniil wins against Nadporozhskyi Oleksii. This market will resolve to 'Nadporozhskyi Oleksii' if Nadporozhskyi Oleksii wins against Habrelyan Daniil. 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 08, 2026 UTC