← Markets

Cassis: Mark Lajal vs Daniel Masur

Tennis Vol. $344,845 50 traders

Mark Lajal100%
Daniel Masur0%
$344,845 Vol. Tennis

Outcomes

16
Chance
Cassis: Mark Lajal vs Daniel Masur
90%
Completed Match
90%
Cassis: Mark Lajal vs Daniel Masur Set 1 Winner Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 2 Winner
90%
Cassis: Mark Lajal vs Daniel Masur Total Sets: O/U 2.5
1%
Cassis: Mark Lajal vs Daniel Masur Set 1 O/U 8.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 1 O/U 9.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 1 O/U 10.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 2 O/U 8.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 2 O/U 9.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Set 2 O/U 10.5
90%
Cassis: Mark Lajal vs Daniel Masur Match O/U 21.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Match O/U 22.5 Resolved
90%
Cassis: Mark Lajal vs Daniel Masur Match O/U 23.5
90%
Cassis: Mark Lajal vs Daniel Masur Set Handicap +/-1.5
90%
Cassis: Mark Lajal vs Daniel Masur Game Spread +/-4.5
1%

Recent trades

  • No recent trades

This market refers to the tennis match between Mark Lajal and Daniel Masur in the Cassis, originally scheduled for September 12, 2026 at 5:30AM ET. This market will resolve to 'Mark Lajal' if Mark Lajal advances against Daniel Masur. This market will resolve to 'Daniel Masur' if Daniel Masur advances against Mark Lajal. If the match is canceled (not played at all), ends in a tie, or a winner has not been determined by September 26, 2026, 11:59 PM ET (14 days after the scheduled start), 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 will be official information from the ATP Tour. A consensus of credible reporting may also be used.

Comments