Mishchenko Oleksandr vs. Krokhmal Vitalii

Mishchenko Oleksandr vs. Krokhmal Vitalii

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

Markets

Mishchenko Oleksandr vs. Krokhmal Vitalii
Mishchenko Oleksandr vs. Krokhmal Vitalii
Ended
 
--
Mishchenko Oleksandr vs. Krokhmal Vitalii: Total Games O/U 3.5
Mishchenko Oleksandr vs. Krokhmal Vitalii Total Games O/U 3.5
Ended
 
--
Mishchenko Oleksandr vs. Krokhmal Vitalii: Total Games O/U 4.5
Mishchenko Oleksandr vs. Krokhmal Vitalii Total Games O/U 4.5
Ended
 
--
Game Handicap: Mishchenko Oleksandr (-1.5) vs Krokhmal Vitalii (+1.5)
Mishchenko Oleksandr vs. Krokhmal Vitalii Game Handicap +/-1.5
Ended
 
--
Game Handicap: Krokhmal Vitalii (-1.5) vs Mishchenko Oleksandr (+1.5)
Mishchenko Oleksandr vs. Krokhmal Vitalii Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Mishchenko Oleksandr and Krokhmal Vitalii in Setka Cup Ukraine Men, scheduled for October 18 at 6:55PM ET. This market will resolve to 'Mishchenko Oleksandr' if Mishchenko Oleksandr wins against Krokhmal Vitalii. This market will resolve to 'Krokhmal Vitalii' if Krokhmal Vitalii wins against Mishchenko Oleksandr. 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 17, 2026 UTC