McNulty's Worlds Gold: The 32km Solo Bet
Tomorrow’s ADAC Cyclassics is billed as a sprinters’ classic. It isn’t, really. Not by the time the peloton reaches Hamburg.
205.7km from Buxtehude to the finish on Mönckebergstraße, and the race gets decided by a 700-meter hill most fans have never heard of, climbed five separate times in the final 50km. The Waseberg tops out at 16% in its steepest pitches. It’s not long. It’s not a mountain. But hit it five times on tired legs and it does something a flat sprint finish never does: it turns “who’s the fastest” into “who’s still there.”
That’s a different problem than the one we usually write about on this site. Flanders tests whether you can pace repeated climbs to save something for the last one. Flèche Wallonne tests whether you can reproduce one specific punch three times under fatigue. The Waseberg tests both of those things and then asks you to sprint at the end anyway — full gas, against riders who’ve been sitting in, after your legs have already answered “can you climb this at threshold, five times” the hard way. Durability first. Finishing kick second. Most amateurs train for one or the other. Almost nobody trains the combination, even though it’s exactly what a hilly Saturday group ride with a sprint for the town sign demands.
Quick Verdict: What the Waseberg Actually Demands
Detail Info Race ADAC Cyclassics, Aug 16, 2026, Buxtehude to Hamburg Distance 205.7km The climb Waseberg: ~700m, gradients up to 16% Ascents 5, all in the final ~50km Field 152 riders, 22 teams (18 WorldTeams, 4 ProTeams) Notable absences Philipsen, Merlier, Pedersen, van Aert Watch for Olav Kooij (2024 winner), Arnaud De Lie, Paul Magnier Defending champion Rory Townsend, won 2025 from an early break The trainable skill Repeated punchy-climb durability plus a preserved neuromuscular sprint — not pure threshold pacing, not a solo attack Amateur equivalent Any hilly group ride that ends in a town-line or café sprint
Look at who isn’t racing tomorrow. Jasper Philipsen, Tim Merlier, Mads Pedersen, and Wout van Aert are all absent from the startlist — four of the sport’s most dangerous pure finishers, gone. That’s not a coincidence of scheduling. Hamburg’s course punishes a certain kind of rider more than most “sprint” races on the calendar, and teams building around a bunch-kick specialist increasingly skip it in favor of races where the finish rewards raw top speed rather than what’s left of it.
What’s left is a field that suits riders who can do both things: survive the Waseberg’s repeated efforts and still have a sprint. Olav Kooij, who won here in 2024, fits that mold. So does Arnaud De Lie, who was second last year, and Paul Magnier, who was third. Rory Townsend won the 2025 edition from an early breakaway that held off the charging bunch by what Cyclingnews described as barely a bike length — a result that only made sense because the Waseberg had already done its work on the group behind him, and the group simply ran out of road to close the gap.
That’s the race, most years. Not “who’s fastest.” Who’s still capable of being fast, after five hard efforts nobody else training for a flat sprint finish would bother preparing for.
The Waseberg is climbed five times in the final 50 kilometers of the 205.7km route from Buxtehude to Hamburg. Each ascent is roughly 700 meters long with sections reaching 16%, short enough to stay in the legs of most riders once or twice but steep and frequent enough, by the fourth and fifth passes, to shed anyone who can’t repeat a hard effort on accumulated fatigue. The final ascent typically comes with well under 10km to race, meaning the selection made there decides who even gets to contest the finish.
We’ve written a lot this year about repeated-climb pacing, because Grand Tours and Classics both keep serving it up. But the Waseberg’s demand is genuinely distinct from what we’ve covered before, and it’s worth being precise about the difference.
Flanders is a pacing discipline problem: go too hard on climb one and you have nothing for climb four. The lesson there is restraint. Flèche Wallonne is a reproducibility problem: can you hit the same 90-second intensity three times under rising fatigue? The lesson there is knowing your specific interval cold. The muri of Tirreno-Adriatico test raw W/kg on short walls with incomplete recovery between them.
The Waseberg borrows pieces of all three — repeated short efforts, incomplete recovery, punchy gradients — and then adds something none of those races require at the finish: a genuine top-end sprint, contested by whoever’s left, often inside the final few hundred meters of flat road after the last climb. That’s a neuromuscular demand, not an aerobic one. Repeated threshold-to-VO2max climbing burns through glycogen and accumulates central fatigue in ways that specifically blunt your ability to fire a maximal sprint afterward. Training the climbs alone doesn’t prepare you for that. Training the sprint alone doesn’t either. You have to train them stacked, in the order the race actually delivers them.
The goal of this session isn’t to get better at climbing or better at sprinting in isolation. It’s to teach your body to produce a maximal sprint effort after your legs have already done five hard, short efforts. That combination — not either half alone — is what separates riders who get dropped by the last climb from riders who get dropped in the sprint after surviving it.
Structure:
RPE: Climb efforts should sit at 8-9/10, hard enough that you’re genuinely working to hold position, not cruising. The recovery blocks between climbs are moderate, not easy — 65-75% FTP is closer to riding through a group than soft-pedaling, which is closer to what actually happens on the road between Waseberg passes. The sprint at the end should be 10/10, everything you have.
What to track: Your peak sprint power on this session versus your peak sprint power fresh, with no preceding climbs. A gap of 15-20% is normal and expected — that’s the fatigue cost of the climbs. A gap over 30-35% means your sprint is collapsing faster than it should under load, which usually points to underdeveloped glycolytic capacity or going too hard on the early climb reps and leaving nothing in reserve.
This one trains the specific pattern of the race — early climbs feel manageable, later ones don’t — by making each rep slightly harder than the last, the way accumulated fatigue actually plays out even when your power stays flat.
Structure:
Why escalate instead of holding steady: Cardiac drift and accumulating fatigue mean the same power output feels progressively harder as a hard effort continues, so a fixed-intensity protocol underestimates what climb five actually costs. Escalating the target intensity forces your body to produce more under worse conditions each time, which is closer to what the Waseberg’s fifth ascent demands after four that came before it.
Five hard efforts across roughly 50km isn’t long enough to bonk in the classic sense, but glycogen availability still determines whether your sprint has anything behind it. Practicing race-day fueling — carbs before the effort starts, not scrambling to eat once the legs are already going — matters more here than on a steady-state ride, because there’s no flat, easy section to catch up on nutrition once the climbing starts. Fuel before the first climb, not between the third and fourth.
You don’t need five weeks of dedicated preparation to get useful adaptation here — two to three weeks of one focused session, plus your normal riding, is enough to notice a difference on a hilly group ride.
Week 1: One Five-Climb Finish Simulation. Establish your baseline sprint-after-fatigue number.
Week 2: One Escalating Climb Reps session, plus a shorter maintenance version of week 1’s workout (3 climb reps instead of 5) if you have a second intensity day available.
Week 3: Repeat the Five-Climb Finish Simulation and compare your sprint power to week 1. If it’s held steady or improved, the adaptation is showing up. If it’s dropped, you likely need another easy week before adding more of this kind of work — it’s a demanding combination and doesn’t tolerate being stacked on top of accumulated fatigue from elsewhere in your training.
If you don’t have access to a real climb, a trainer with resistance turned up or even a headwind section works for the climb reps — the specific gradient matters less than replicating the intensity-then-recovery-then-sprint sequence.
If you’re tuning in, the race tells its own story before the finish line does. Watch the group size on the fourth Waseberg ascent — that’s usually the clearest signal of who’s actually contesting the finish versus who’s about to be a spectator. Kooij’s team, and Lotto’s for De Lie, will likely try to control the pace on the climbs specifically to keep the group as large as possible for as long as possible, since a smaller group generally favors whoever has the strongest legs left, not necessarily their own sprinter. Watch for exactly the kind of early break that worked for Townsend last year — on a course this selective, a well-timed move can survive precisely because the group behind it is busy being whittled down by the same climbs the break already got through.
Most training content about repeated climbs is really about pacing discipline — go easier early so you have more late. That’s true here too, but it’s only half the answer. The Waseberg doesn’t just ask whether you can survive five hard efforts. It asks whether anything’s left afterward for the one effort that actually decides the race.
That’s the gap in a lot of amateur preparation for hilly group rides and town-line sprints: riders train the climbing or they train the sprint, rarely both in the sequence the road actually delivers them. If your Saturday rides end with a contested sprint after a hilly route, the Waseberg’s lesson applies directly — the climbs aren’t the test. What you have left after them is.
Route, field size, and Waseberg climb data from the official ADAC Cyclassics site and ProCyclingUK’s 2026 contenders preview. 2025 result and finish details from Cyclingnews. Kooij’s 2024 win and rider history from ProCyclingStats. Training targets are estimates based on power-based training principles — adjust for your own tested FTP and how your sprint responds to fatigue.