Schmidtmayer Frantisek vs. Melisek Marian

Schmidtmayer Frantisek vs. Melisek Marian

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Czechia MenSportsTable Tennis
$0 Total VolOct 02, 2026 UTC

Markets

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

Rules

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