Melisek Marian vs. Schmidtmayer Frantisek

Melisek Marian vs. Schmidtmayer Frantisek

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Czechia MenSportsTable Tennis
$0 Total VolSep 18, 2026 UTC

Markets

Melisek Marian vs. Schmidtmayer Frantisek
Melisek Marian vs. Schmidtmayer Frantisek
Ended
 
--
Melisek Marian vs. Schmidtmayer Frantisek: Total Games O/U 3.5
Melisek Marian vs. Schmidtmayer Frantisek Total Games O/U 3.5
Ended
 
--
Melisek Marian vs. Schmidtmayer Frantisek: Total Games O/U 4.5
Melisek Marian vs. Schmidtmayer Frantisek Total Games O/U 4.5
Ended
 
--
Game Handicap: Melisek Marian (-1.5) vs Schmidtmayer Frantisek (+1.5)
Melisek Marian vs. Schmidtmayer Frantisek Game Handicap +/-1.5
Ended
 
--
Game Handicap: Schmidtmayer Frantisek (-1.5) vs Melisek Marian (+1.5)
Melisek Marian vs. Schmidtmayer Frantisek Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Melisek Marian and Schmidtmayer Frantisek in Setka Cup Czechia Men, scheduled for September 11 at 7:30AM ET. This market will resolve to 'Melisek Marian' if Melisek Marian wins against Schmidtmayer Frantisek. This market will resolve to 'Schmidtmayer Frantisek' if Schmidtmayer Frantisek wins against Melisek Marian. 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 10, 2026 UTC