Corghencea Radomir vs. Salcutan Veaceslav

Corghencea Radomir vs. Salcutan Veaceslav

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

Markets

Corghencea Radomir vs. Salcutan Veaceslav
Corghencea Radomir vs. Salcutan Veaceslav
Ended
 
--
Corghencea Radomir vs. Salcutan Veaceslav: Total Games O/U 3.5
Corghencea Radomir vs. Salcutan Veaceslav Total Games O/U 3.5
Ended
 
--
Corghencea Radomir vs. Salcutan Veaceslav: Total Games O/U 4.5
Corghencea Radomir vs. Salcutan Veaceslav Total Games O/U 4.5
Ended
 
--
Game Handicap: Corghencea Radomir (-1.5) vs Salcutan Veaceslav (+1.5)
Corghencea Radomir vs. Salcutan Veaceslav Game Handicap +/-1.5
Ended
 
--
Game Handicap: Salcutan Veaceslav (-1.5) vs Corghencea Radomir (+1.5)
Corghencea Radomir vs. Salcutan Veaceslav Game Handicap +/-1.5
Ended
 
--

Rules

This market refers to the table tennis match between Corghencea Radomir and Salcutan Veaceslav in Setka Cup Moldova Men, scheduled for September 25 at 1:30PM ET. This market will resolve to 'Corghencea Radomir' if Corghencea Radomir wins against Salcutan Veaceslav. This market will resolve to 'Salcutan Veaceslav' if Salcutan Veaceslav wins against Corghencea Radomir. 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