Training for a mountain ultra: vertical gain, time on feet and pacing
A mountain ultra isn't just a longer road race. The clock is dominated by climbing, descending and terrain — not by your flat 5K pace. If you train it like a road marathon, the mountain will find you out. Here's what actually moves the needle, and how a data-driven plan keeps it honest.
Vertical gain is a training metric, not a footnote
On steep ground, elevation gain often costs you more than distance. Two 30 km runs with 500 m and 2,000 m of climbing are completely different sessions. So plan and track your week in two dimensions: distance and vertical (D+). Building the legs and lungs to climb — and, just as importantly, to descend — is the work that decides your race.
When a source provides GPS and an elevation profile, Rurilab can put climbing alongside your activity history. Missing routes and elevation estimates must keep their limitations visible. That lets your weekly vert build as deliberately as your mileage.
Think in time on feet, not just kilometres
At altitude and on technical trails you move slowly, and a long day can mean many hours upright. Time on feet — total duration — is frequently a better guide to the training stress of a mountain run than distance. A five-hour hike-run with big climbing is a serious session even if the kilometre count looks modest.
Long back-to-back weekends (a big day followed by another on tired legs) are a classic ultra tool: they rehearse racing on fatigue without the need to complete the race distance in one session. They are not automatically safer or suitable for every runner; recovery and recent training need to guide the choice.
Downhill running is a skill — and a cost
Descending fast is trainable, but the eccentric muscle damage from long descents is real and slow to recover. Neglect downhills in training and your quads will fail before your heart or lungs do on race day. Deliberately practise descending, and respect that a descent-heavy session needs recovery like any hard workout.
Pace by effort, not by pace
Your flat goal pace is meaningless going up a 20% grade. In the mountains, steer by effort and heart rate (and, for many, by when to power-hike versus run). Even the strongest mountain runners hike the steep pitches — walking efficiently uphill is a skill worth training, not a failure.
Rurilab's paces come from your fitness (VDOT) for the runnable stuff, but its daily read leans on heart rate, load and recovery — the signals that still make sense when the terrain throws pace out the window.
Specificity: train the race you're running
- Match the terrain. If your race is technical and steep, spend real time on technical, steep ground — not only smooth trails or the treadmill.
- Rehearse the climbs and descents your course demands, ideally with similar total D+.
- Practise fueling and hiking at the efforts and durations you'll actually race at.
- Simulate conditions — heat, altitude, night, a loaded vest — where you safely can.
Recover like the training is hard, because it is
Big vert and long descents generate load that a mileage number alone hides. Tracking training load (CTL/ATL/TSB) alongside resting heart rate, HRV and sleep can add context when data are available. These signals do not prove recovery or prevent injury. A plan should account for your response and missing information rather than treating a model score as permission for another hard mountain day.
A simple framework
- Base: aerobic volume, easy running, gradual vert.
- Build: race-specific climbing and descending, long back-to-backs, fueling practice.
- Peak: your biggest mountain-specific days, then
- Taper: shed fatigue while holding fitness, so you arrive fresh.
None of it is exotic — it's endurance fundamentals, pointed at vertical terrain and long hours, and adjusted to how your body is actually absorbing the work.