Hrabskyi Andrii vs. Marushchak Vitalii S.

Hrabskyi Andrii vs. Marushchak Vitalii S.

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

Markets

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

Rules

This market refers to the table tennis match between Hrabskyi Andrii and Marushchak Vitalii S. in Setka Cup Ukraine Men, scheduled for September 7 at 12:40PM ET. This market will resolve to 'Hrabskyi Andrii' if Hrabskyi Andrii wins against Marushchak Vitalii S.. This market will resolve to 'Marushchak Vitalii S.' if Marushchak Vitalii S. wins against Hrabskyi Andrii. 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 06, 2026 UTC