Marushchak Vitalii S. vs. Levshyn Anatolii

Marushchak Vitalii S. vs. Levshyn Anatolii

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

Markets

Marushchak Vitalii S. vs. Levshyn Anatolii
Marushchak Vitalii S. vs. Levshyn Anatolii
Ended
 
--
Marushchak Vitalii S. vs. Levshyn Anatolii: Total Games O/U 3.5
Marushchak Vitalii S. vs. Levshyn Anatolii Total Games O/U 3.5
Ended
 
--
Marushchak Vitalii S. vs. Levshyn Anatolii: Total Games O/U 4.5
Marushchak Vitalii S. vs. Levshyn Anatolii Total Games O/U 4.5
Ended
 
--
Game Handicap: Marushchak Vitalii S. (-1.5) vs Levshyn Anatolii (+1.5)
Marushchak Vitalii S. vs. Levshyn Anatolii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Levshyn Anatolii (-1.5) vs Marushchak Vitalii S. (+1.5)
Marushchak Vitalii S. vs. Levshyn Anatolii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Marushchak Vitalii S. and Levshyn Anatolii in Setka Cup Ukraine Men, scheduled for August 17 at 7:40AM ET. This market will resolve to 'Marushchak Vitalii S.' if Marushchak Vitalii S. wins against Levshyn Anatolii. This market will resolve to 'Levshyn Anatolii' if Levshyn Anatolii wins against Marushchak Vitalii S.. 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 16, 2026 UTC