Karnaukh Mykola vs. Mykhalchenko Volodymyr

Karnaukh Mykola vs. Mykhalchenko Volodymyr

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolAug 30, 2026 UTC

Markets

Karnaukh Mykola vs. Mykhalchenko Volodymyr
Karnaukh Mykola vs. Mykhalchenko Volodymyr
Ended
 
--
Karnaukh Mykola vs. Mykhalchenko Volodymyr: Total Games O/U 3.5
Karnaukh Mykola vs. Mykhalchenko Volodymyr Total Games O/U 3.5
Ended
 
--
Karnaukh Mykola vs. Mykhalchenko Volodymyr: Total Games O/U 4.5
Karnaukh Mykola vs. Mykhalchenko Volodymyr Total Games O/U 4.5
Ended
 
--
Game Handicap: Karnaukh Mykola (-1.5) vs Mykhalchenko Volodymyr (+1.5)
Karnaukh Mykola vs. Mykhalchenko Volodymyr Game Handicap +/-1.5
Ended
 
--
Game Handicap: Mykhalchenko Volodymyr (-1.5) vs Karnaukh Mykola (+1.5)
Karnaukh Mykola vs. Mykhalchenko Volodymyr Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Karnaukh Mykola and Mykhalchenko Volodymyr in Setka Cup Ukraine Men, scheduled for August 23 at 2:30PM ET. This market will resolve to 'Karnaukh Mykola' if Karnaukh Mykola wins against Mykhalchenko Volodymyr. This market will resolve to 'Mykhalchenko Volodymyr' if Mykhalchenko Volodymyr wins against Karnaukh Mykola. 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 Aug 22, 2026 UTC