2018 Tour de France: Stage 7 Preview
By Cycling News
Fougères - Chartres, 231km
The most difficult part of this stage is its length. Stage 7 is the longest this year with 231km.
Leaving Brittany from Fougères, the home of former yellow jersey Georges Groussard (nine days in 1964), former Tour de France technical director Albert Bouvet and current Fortuneo-Samsic team manager Emmanuel Hubert, the race visits the cycling mad provinces of Mayenne and Sarthe throughout the undulated "Alpes mancelles" at half way into Chartres and its famous cathedral.
On the Tour's last visit in 2004, it wasn't a bunch sprint finish, but Stuart O'Grady won from a breakaway and Thomas Voeckler started his first odyssey in yellow. The finishing area of the Beauce can be windy and favour echelons.
The other factor to reduce the probability of a bunch gallop is the teams being down to eight men. After one week of racing, they won't have the super power of cancelling all breakaway attempts like before.
Matt White says: On paper this is a really simple stage but that’s not to be confused with calling it easy. You’ve got to manage your resources for stages like this, and rotate your riders between the TTT and the Roubaix stage.
Latest on Cyclingnews
-
Tom Pidcock closes Opening Weekend with third in Kuurne-Brussel-Kuurne
Ineos Grenadiers rider makes the podium after strong showing in Omloop -
Mads Pedersen wins Kuurne-Brussel-Kuurne
Trek-Segafredo rider wins sprint as Mathieu van der Poel and breakaway are caught in closing kilometres -
How to watch Kuurne-Brussel-Kuurne 2021 – live TV and streaming
Kristoff, Van Avermaet, Pedersen, Degenkolb and more to do battle on second day of Opening Weekend -
Kuurne-Brussel-Kuurne - Live coverage
Follow live race text coverage from Belgium
Sign up to the Cyclingnews Newsletter. You can unsubscribe at any time. For more information about how to do this, and how we hold your data, please see our privacy policy
Thank you for signing up to Cycling News. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.