Tiutiunnyk Maksym vs. Skorobahatyi Yevhen

Tiutiunnyk Maksym vs. Skorobahatyi Yevhen

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Ukraine MenSportsTable Tennis
$0 Total VolOct 31, 2026 UTC

Markets

Tiutiunnyk Maksym vs. Skorobahatyi Yevhen
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen
Ended
 
--
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen: Total Games O/U 3.5
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen Total Games O/U 3.5
Ended
 
--
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen: Total Games O/U 4.5
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen Total Games O/U 4.5
Ended
 
--
Game Handicap: Tiutiunnyk Maksym (-1.5) vs Skorobahatyi Yevhen (+1.5)
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen Game Handicap +/-1.5
Ended
 
--
Game Handicap: Skorobahatyi Yevhen (-1.5) vs Tiutiunnyk Maksym (+1.5)
Tiutiunnyk Maksym vs. Skorobahatyi Yevhen Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Tiutiunnyk Maksym and Skorobahatyi Yevhen in Setka Cup Ukraine Men, scheduled for October 24 at 1:10PM ET. This market will resolve to 'Tiutiunnyk Maksym' if Tiutiunnyk Maksym wins against Skorobahatyi Yevhen. This market will resolve to 'Skorobahatyi Yevhen' if Skorobahatyi Yevhen wins against Tiutiunnyk Maksym. 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 Oct 23, 2026 UTC