LiontipsDe Minaur vs. Struff. Olympic Match Prediction and Bets
Command Analysis
De Minaur has not yet played official matches since Wimbledon. At the London major, Alex managed to show a pretty good result. In London, he reached the quarterfinals, where he was unable to play Novak Djokovic due to a leg injury. On clay, the Australian has ten wins and five losses this season. At Roland Garros, De Minaur made it to the quarterfinals of the tournament.
Struff took part in the clay tournament in Gstaad on the eve of the Olympics in Paris, where he managed to secure a place in the semi-finals of the competition - at this stage he lost to Quentin Gali. On clay, Jan-Lennard has 14 victories and five defeats this season, and one title. In April, the German secured a victory at the home competition in Munich - in the final he beat Taylor Fritz.
Tip and bets
De Minaur has not played since Wimbledon. Then, let us recall, he was unable to go out for the quarterfinal match against Djokovic due to a leg injury. So we are not sure that Alex is 100% ready for the Olympics in Paris. We think that in this pair, preference should be given to Struff.
Our prediction is Struff's victory with odds of 1.81 in BC Fonbet
Bet on total
The last face-to-face encounter between the tennis players took place this season at Roland Garros and was played over the top. We believe that the next face-to-face meeting between De Minaur and Struff will also be over the top.
The second forecast is total over 22 games for odds of 1.83 in BC Zenit
Bet on the first set
Three of Struff's last five matches have seen the first set go to more than 9.5 games. We expect the upcoming Jan-Lennard vs. De Minaur match to also start with a top first set.
Forecast - total over 9.5 games in the first set for odds of 1.89
Betting predictions stat
Explore all statistics
Trends
Bet Tie-break in the match - yes
This bet has played in 3 of Struff's previous 5 matches
2.36Rate Set Result: 1>2
In 3 of De Minaur's last 5 matches, events on the court have unfolded according to this scenario
2.18