Kovalchuk Vladyslav vs. Fashchevskyi Ivan

Kovalchuk Vladyslav vs. Fashchevskyi Ivan

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

Markets

Kovalchuk Vladyslav vs. Fashchevskyi Ivan
Kovalchuk Vladyslav vs. Fashchevskyi Ivan
Ended
 
--
Kovalchuk Vladyslav vs. Fashchevskyi Ivan: Total Games O/U 3.5
Kovalchuk Vladyslav vs. Fashchevskyi Ivan Total Games O/U 3.5
Ended
 
--
Kovalchuk Vladyslav vs. Fashchevskyi Ivan: Total Games O/U 4.5
Kovalchuk Vladyslav vs. Fashchevskyi Ivan Total Games O/U 4.5
Ended
 
--
Game Handicap: Kovalchuk Vladyslav (-1.5) vs Fashchevskyi Ivan (+1.5)
Kovalchuk Vladyslav vs. Fashchevskyi Ivan Game Handicap +/-1.5
Ended
 
--
Game Handicap: Fashchevskyi Ivan (-1.5) vs Kovalchuk Vladyslav (+1.5)
Kovalchuk Vladyslav vs. Fashchevskyi Ivan Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Kovalchuk Vladyslav and Fashchevskyi Ivan in Setka Cup Ukraine Men, scheduled for August 18 at 11:05AM ET. This market will resolve to 'Kovalchuk Vladyslav' if Kovalchuk Vladyslav wins against Fashchevskyi Ivan. This market will resolve to 'Fashchevskyi Ivan' if Fashchevskyi Ivan wins against Kovalchuk Vladyslav. 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 17, 2026 UTC