Hrynenko Kostiantyn vs. Kulishov Hryhorii

Hrynenko Kostiantyn vs. Kulishov Hryhorii

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolNov 10, 2026 UTC

Markets

Hrynenko Kostiantyn vs. Kulishov Hryhorii
Hrynenko Kostiantyn vs. Kulishov Hryhorii
Ended
 
--
Hrynenko Kostiantyn vs. Kulishov Hryhorii: Total Games O/U 3.5
Hrynenko Kostiantyn vs. Kulishov Hryhorii Total Games O/U 3.5
Ended
 
--
Hrynenko Kostiantyn vs. Kulishov Hryhorii: Total Games O/U 4.5
Hrynenko Kostiantyn vs. Kulishov Hryhorii Total Games O/U 4.5
Ended
 
--
Game Handicap: Hrynenko Kostiantyn (-1.5) vs Kulishov Hryhorii (+1.5)
Hrynenko Kostiantyn vs. Kulishov Hryhorii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Kulishov Hryhorii (-1.5) vs Hrynenko Kostiantyn (+1.5)
Hrynenko Kostiantyn vs. Kulishov Hryhorii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Hrynenko Kostiantyn and Kulishov Hryhorii in Setka Cup Ukraine Men, scheduled for November 2 at 10:35PM ET. This market will resolve to 'Hrynenko Kostiantyn' if Hrynenko Kostiantyn wins against Kulishov Hryhorii. This market will resolve to 'Kulishov Hryhorii' if Kulishov Hryhorii wins against Hrynenko Kostiantyn. 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 Nov 02, 2026 UTC