Updated September 2026

Trail running pace is nothing like road running pace. A runner who comfortably runs 6 minute kilometres on road will be closer to 8 or 9 minutes per kilometre on mixed trail with any meaningful elevation. Add fell terrain or deep mud and the gap widens further. Understanding why, and being able to estimate your trail pace before a race, is one of the most useful things you can do as a trail runner.

This calculator uses Naismith’s Rule, the standard formula for estimating mountain travel time, adjusted for trail terrain type. Enter your flat road pace, the elevation gain per kilometre of your route and the terrain you are running on and it will give you an adjusted trail pace, estimated finish time and how much slower than road pace you can expect to run.

Trail Running Pace Calculator – Kilometres


6:00


50m


20km

Adjusted trail pace

—

min/km

Estimated finish time

—

total

Slower than road

—

min/km

Move the sliders above to calculate your trail pace.

Based on Naismith’s Rule adjusted for trail terrain. An estimate only — actual pace depends on fitness, conditions and technical skill.

 

Trail Running Pace Calculator — Miles


10:00


165ft


13 miles

Adjusted trail pace

—

min/mile

Estimated finish time

—

total

Slower than road

—

min/mile

Move the sliders above to calculate your trail pace.

Based on Naismith’s Rule adjusted for trail terrain. Elevation penalty: 1 min added per 33ft of climb per mile. An estimate only — actual pace depends on fitness, conditions and technical skill.

Why Trail Pace Is So Different From Road Pace

Road running is consistent. The surface is flat, the gradient is minimal and your foot strikes the same way with every stride. Trail running is the opposite — varied terrain, constant gradient changes, technical ground that demands your attention and significant elevation gain that slows you down far more than most runners expect.

The elevation penalty is the single biggest factor. Naismith’s Rule, developed by Scottish mountaineer William Naismith in 1892 and still used by mountain rescue teams today, adds one hour per 600 metres of ascent to any journey time. In practical terms for runners this means roughly one extra minute per kilometre for every 10 metres of climbing per kilometre. A route with 100 metres of elevation gain per kilometre will take roughly 10 minutes per kilometre longer than the same distance on flat ground — before terrain is even factored in.

Terrain adds another layer on top. Hard packed trail on a dry day runs close to road pace. Technical rocky trail demands more attention and more energy per stride. Fell and open mountain terrain in wet conditions can be twice as slow as road running at the same effort level. Deep mud in October adds weight to every foot strike and makes even moderate gradients genuinely hard work.

How to Use This Calculator

Flat road pace — enter your comfortable road running pace in minutes per kilometre. Use your easy training pace rather than your race pace for most trail runs. If you are estimating a race finish time use your goal race pace.

Elevation gain per km — divide the total elevation gain of your route by the distance in kilometres. A 20 kilometre route with 800 metres of total ascent has 40 metres of elevation gain per kilometre. You can find elevation data for most routes on Strava, Komoot or OS Maps.

Distance — the total distance of your run or race in kilometres.

Terrain type — choose the terrain that best describes the majority of your route. If your route mixes terrain types choose the one that covers the most ground or err toward the more technical option for a conservative estimate.

Trail Pace vs Road Pace — Real World Examples

To give you a sense of how the calculator works in practice, here are some typical scenarios based on coaching runners at different levels.

A runner with a 5 minute 30 second per kilometre road pace running a flat hard packed trail 10k with no elevation will be close to that pace — perhaps 5 minutes 45 seconds per kilometre once terrain friction is accounted for.

The same runner on a 25 kilometre fell race with 60 metres of elevation gain per kilometre on open mountain terrain would be looking at something closer to 10 to 11 minutes per kilometre — nearly twice as slow, at the same effort level. That is completely normal. Fell racing pace is not comparable to road racing pace and experienced fell runners do not try to make that comparison.

For ultra marathon distances of 50 kilometres and beyond with significant elevation the finish time calculation becomes even more important. Runners who set off at road-influenced pace in an ultra almost always pay for it in the final third of the race when their legs have accumulated the debt of that early optimism.

Pacing Strategy for Trail Races

The most common mistake trail runners make, particularly those coming from a road running background, is going out too fast in the early miles. Road pace instincts do not translate to trail. A section that feels comfortable at mile two because it is runnable flat trail will cost you at mile fifteen when the sustained climbing arrives and your legs have already spent energy they needed to save.

Run by effort on trail, not by pace. Your GPS watch is a useful tool for navigation and distance tracking on trail but the pace figure it shows you on a climb is largely meaningless as a performance indicator. A 15 minute per kilometre pace on a steep mountain section may represent exactly the right effort. A 7 minute per kilometre pace on the same section may be catastrophically fast.

Walk the steep climbs without apology. The best trail and ultra runners in the world power hike sustained gradients because it is faster and more economical than trying to run them. Give yourself permission to walk uphills from your very first trail race. You will go further and finish stronger.

See our full guide to training for your first fell race for more detail on pacing strategy and what to expect on race day. For runners switching from road to trail our road to trail running guide covers the full adjustment in depth.

Trail Running Shoes for Different Terrain

The terrain type you select in the calculator also has direct implications for your footwear choice. The right shoe for hard packed dry trail is not the right shoe for deep autumn mud and the difference in grip, confidence and energy expenditure is significant.

For mixed trail the Hoka Speedgoat 7 with its Vibram Megagrip outsole handles the widest range of conditions. For technical rocky terrain the Inov-8 Trailfly Speed’s graphene grip is specifically engineered for wet rock. For deep mud the Salomon Speedcross 6 with its 8mm chevron lugs is the right specialist choice. See our full best trail running shoes guide for current recommendations.

Tracking Your Trail Pace

A GPS watch with grade-adjusted pace is the most useful tool for managing effort on trail runs and races. Grade adjusted pace shows your equivalent flat effort on a climb rather than the raw pace which spikes wildly on every uphill section. On a fell race or mountain ultra this feature alone changes how you pace your effort across many hours of varied terrain.

See our guides to the best Garmin watches for trail running and our Garmin Fenix 8 vs Forerunner 970 comparison for current recommendations.

Frequently Asked Questions

How much slower is trail running than road running?

As a rough starting point trail running is typically one and a half to two minutes per kilometre slower than road running at the same effort on mixed terrain with moderate elevation. On technical fell terrain with significant climbing the gap can be three minutes per kilometre or more. Use this calculator with your specific route elevation data for a more accurate estimate.

What is Naismith’s Rule?

Naismith’s Rule is a formula developed by Scottish mountaineer William Naismith in 1892 for estimating travel time in the mountains. It adds one hour per 600 metres of ascent to the base travel time for a given distance. It remains the standard method used by mountain rescue teams and outdoor professionals for journey planning in hilly terrain. This calculator applies a modified version adjusted for running pace rather than walking pace.

How do I find the elevation gain for my route?

Strava, Komoot and OS Maps all show elevation data for recorded or planned routes. Divide the total elevation gain in metres by the distance in kilometres to get the metres of gain per kilometre to enter into this calculator.

Should I use my race pace or training pace in the calculator?

For estimating race finish times use your goal race pace or a realistic recent race pace from a comparable distance. For planning training runs use your easy training pace. If you are unsure err toward a slower pace — it is better to finish a trail race with energy left than to blow up at mile 20 because your pace estimate was too optimistic.

Why does terrain type affect pace so much?

Different terrain types demand different levels of concentration, different muscle recruitment patterns and different energy expenditure per stride. Technical rocky trail requires constant foot placement decisions that slow you down beyond the pure gradient effect. Deep mud adds weight to every stride and reduces propulsion. Fell terrain on open mountain involves all of these factors simultaneously alongside often unpredictable ground conditions.

Is this calculator suitable for fell racing?

Yes — select Fell and open mountain as the terrain type for fell racing estimates. Note that GPS watches are not permitted in fell races themselves, though they are useful for training. See our guide to training for your first fell race for more on fell racing specifically.

Meta description: Calculate your trail running pace adjusted for elevation gain and terrain type. Based on Naismith’s Rule — enter your road pace and route details for an instant trail pace estimate.

Suggested URL: /trail-running-pace-calculator

Focus keyword: trail running pace calculator

Replace [YOUR WPCODE SHORTCODE HERE] with the shortcode WPCode generated for your HTML snippet. The calculator sits between the intro and the explanatory content which is exactly where visitors expect to find it — read the intro, use the tool, read the context around it.

Write a message…