How to pace trail runs by elevation gain

Why min/km breaks on trails

The energy cost of running rises steeply with gradient: at 6:00/km on the flat you might be jogging comfortably, while the same pace on a 10% climb would be close to maximal for most runners. Research on gradient running shows the cost per kilometre climbs far faster than intuition suggests, and GPS pace adds noise on switchbacks and under tree cover. So a pace target that made sense on the road becomes meaningless the moment the trail tilts. The fix is not a better pace target — it is changing the unit you plan with.

The km-effort rule: 100 m of climb ≈ 1 km flat

A robust field heuristic used across trail running: every 100 m of elevation gain costs about the same effort as one extra kilometre on the flat. Effort-distance = distance + (elevation gain ÷ 100). A 25 km race with 1,200 m of climbing is therefore ≈ 37 effort-km — closer to a road marathon in effort than to a 25 km road race. Use it to compare races, size long runs, and sanity-check a weekly plan. It is a planning heuristic, not a physical law: technical terrain, altitude and very steep grades push the real cost higher. You can run your own numbers with our trail-to-road effort calculator.

Pace climbs by vertical speed, not pace

On a sustained climb, the number that describes your output is vertical speed — metres climbed per hour (often called VAM). Measure yours on a repeatable local climb: time the ascent, divide the vert by the hours. Many trained trail runners sustain roughly 600–900 m/h on runnable grades; strong racers exceed 1,000–1,200 m/h. Two practical consequences: above a certain steepness, hiking with a strong posture (or poles) is more economical than running — even elite racers hike — and your watch's grade-adjusted pace (GAP) is only an approximation of flat-equivalent effort. Heart rate and breathing remain the honest governors on a climb.

Downhills are not free

Descents read as fast pace and low heart rate, which makes them easy to dismiss in planning — but the eccentric (braking) muscle load is exactly what destroys quads late in long races. If your goal race loses serious altitude, your legs must practise losing altitude: include progressive downhill segments in training, focus on cadence and line choice rather than braking, and count descent in your session load even when the pace looks easy. Post-race soreness after a mountain event comes mostly from the down, not the up.

Plan by time and vert, not kilometres

The practical system: express weekly volume in hours plus weekly elevation gain, size long runs by duration (with a vert target when preparing a mountain race), and let effort-distance translate between road fitness and trail ambitions. Your race preparation should progressively approach the race's elevation profile, not just its distance — that is how our trail and ultra training plans are structured. This is exactly how Coach Leo builds trail plans — sessions are prescribed in time and climb, synced against what you actually ran on Strava or Suunto, and adjusted when your real vertical speed says the plan was too ambitious or too shy.

Frequently asked questions