Grimaldi Alessio vs. Iskander Christopher

Grimaldi Alessio vs. Iskander Christopher

$0 Liq5 MarketsSource
GamesSetkaSetka Cup Moldova MenSportsTable Tennis
$0 Total VolSep 08, 2026 UTC

Markets

Grimaldi Alessio vs. Iskander Christopher
Grimaldi Alessio vs. Iskander Christopher
Ended
 
--
Grimaldi Alessio vs. Iskander Christopher: Total Games O/U 3.5
Grimaldi Alessio vs. Iskander Christopher Total Games O/U 3.5
Ended
 
--
Grimaldi Alessio vs. Iskander Christopher: Total Games O/U 4.5
Grimaldi Alessio vs. Iskander Christopher Total Games O/U 4.5
Ended
 
--
Game Handicap: Grimaldi Alessio (-1.5) vs Iskander Christopher (+1.5)
Grimaldi Alessio vs. Iskander Christopher Game Handicap +/-1.5
Ended
 
--
Game Handicap: Iskander Christopher (-1.5) vs Grimaldi Alessio (+1.5)
Grimaldi Alessio vs. Iskander Christopher Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Grimaldi Alessio and Iskander Christopher in Setka Cup Moldova Men, scheduled for September 1 at 11:15AM ET. This market will resolve to 'Grimaldi Alessio' if Grimaldi Alessio wins against Iskander Christopher. This market will resolve to 'Iskander Christopher' if Iskander Christopher wins against Grimaldi Alessio. 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 Aug 31, 2026 UTC