How to Use a Pace Calculator to Pace a Trail Marathon (2026)

The men’s road marathon world record sits at 2:00:35. The men’s record at the Pikes Peak Marathon, a 42 km out-and-back course with 2,400 m of elevation gain, is 3:16:39. Same distance. Two and a quarter wasted hours, give or take. That gap is not a story about who is fitter. It is a story about what a flat-road pace target actually means once the ground starts climbing, the trail narrows, and you have to walk past a queue at an aid station. The runners who finish trail marathons inside their goal time are not the fittest in the field. They are the ones who turned a road pace into an honest trail pace before they started.

This guide walks you through how to use a standard pace calculator as the starting point for trail marathon pacing, how to layer on the adjustments that actually matter, and how to lock the result into splits you can race off without overcooking it on the first climb.

Why a Flat Road Pace Cannot Be Your Trail Marathon Pace

A road marathon punishes you for going too fast. A trail marathon punishes you for not adjusting at all. Three forces stack against the clock the moment you leave tarmac, and each one is measurable.

The first is elevation. Minetti and colleagues, writing in the Journal of Applied Physiology (2002), measured the energy cost of running at gradients between -45% and +45% and produced the data that every modern grade-adjusted pace algorithm leans on. The headline: each 1% of positive gradient adds roughly 12 to 15 seconds per kilometre to the metabolic cost of holding the same effort. A 7% climb that lasts 2 km costs you roughly 90 seconds you cannot win back on the descent, because steep downhills carry their own braking cost once the gradient drops below -10%.

The second is terrain. Vernillo and colleagues, in a 2017 Sports Medicine review on the physiology of trail running, found that uneven, technical ground raises the energy cost of running by another 10% to 30% above a smooth surface, even before elevation is counted. Roots, rocks and loose gravel force micro-adjustments in stride length, foot strike and trunk control, and the cost of those adjustments shows up on your watch as a slower pace at a higher heart rate.

The third is everything that is not running. Trail marathons mean aid stations you have to walk through to refill bottles, gates and stiles that force a stop, occasional queues on single-track climbs, and the simple fact that even strong runners hike steep climbs because hiking is faster than failed running. The International Trail Running Association’s coefficient system, used to estimate finish times across courses, assumes a non-running fraction of 5% to 20% of total time depending on terrain. On a 5-hour trail marathon, that is 15 to 60 minutes you will not be moving at running pace.

Start With Your Flat Pace, Then Adjust

The whole job of a road pace calculator in trail planning is to give you a clean baseline. You enter the marathon time you would target on flat tarmac in good conditions, and the tool returns the per-kilometre and per-mile pace you would need to hold. That number is the floor of the calculation, not the answer.

From there you stack three adjustments on top: an elevation cost, a terrain cost, and a non-running allowance. Do them in that order. Each one builds on the last, and skipping any of them is how runners end up writing race reports about hitting the wall at 28 km on a climb that looked harmless on the elevation profile.

Calculate Pace

Adjustment one: elevation cost

Total elevation gain is on every race brief. Convert it into a finish-time penalty using a working figure that lines up with both Minetti’s data and the GAP algorithms used by Strava and Garmin: roughly 60 seconds added to total finish time for every 100 m of climb. A 42 km race with 1,200 m of gain therefore costs you about 12 minutes on top of your flat marathon time, even before terrain is counted. To turn that course-average cost into a specific pace target on the climbs themselves, run the gain through the Hill Grade Adjusted Pace calculator on the steepest 2 km section of the course and let the maths show you what holding effort actually looks like on that climb.

Adjustment two: terrain cost

Apply a multiplier based on the surface. Smooth fire road or canal towpath adds nothing. Buffed singletrack adds 5% to 10% to the post-elevation pace. Technical singletrack with roots and rocks adds 10% to 20%. Loose scree, bog or sustained mud adds 20% to 30% or more. Race reports from previous years are the cleanest source: search the race name plus the year and read three of them. Average finish times in the middle of the pack tell you the terrain truth no race website will.

Adjustment three: non-running allowance

Add a flat block of minutes for everything that is not forward running. Two minutes per aid station you intend to refill at. One minute per kit check or gate. Two to five minutes for hike-walks on climbs steeper than 12% to 15%. On a course with five aid stations, two big climbs and a kit check at halfway, that is comfortably 25 to 35 minutes you should be planning for. Add this as a block at the end. It is the difference between a goal time and a fantasy time.

A Worked Example You Can Copy

Take a runner whose recent flat marathon is 3:45, which translates to a target pace of about 5:20 per kilometre on a road course in good conditions. Their target race is a 42 km trail marathon with 1,200 m of gain on rolling singletrack, with five aid stations and one kit check at halfway.

• Flat baseline: 5:20 per kilometre, total 3:45 of pure running.
• Elevation adjustment: 1,200 m of gain at 60 seconds per 100 m adds 12 minutes. New running time: 3:57.
• Terrain adjustment: Rolling singletrack at 8% adds about 19 minutes to a 3:57 base. New running time: 4:16.
• Non-running allowance: Five aid stations at 2 minutes each, one kit check at 2 minutes, plus 6 minutes of hike-walks on the two main climbs. Total: 18 minutes. Final goal time: 4:34.

The same runner trying to defend the 3:45 road target on the trail finishes the first 10 km on pace, blows through the climb at 22 km, loses 20 minutes on the second climb, and walks the last 5 km, in many cases recording 5:10 or worse. The runner who planned for 4:34 hits the first climb under control, banks effort for the second one, and finishes inside their target. Same fitness. Different plan.

Once you have the adjusted finish time, drop it into the Race Time Predictor to sanity check the per-kilometre demand against your recent training, then lock the kilometre band into a split time calculator so you can carry the splits on your wrist on race day.

Four Steps to Lock the Plan In

1. Pull your flat marathon pace. Use your honest current fitness, not last year’s PR. Plug your recent half-marathon or 10 km time into the Race Time Predictor to get a marathon-equivalent baseline if you have not raced the distance this season.
2. Layer the three adjustments in order. Elevation first, terrain second, non-running last. Doing them in the wrong order makes the maths cleaner-looking but the result wrong.
3. Split the race into three blocks. First third: aim 5 to 10 seconds per kilometre slower than your adjusted pace. Middle third: hold the adjusted pace. Last third: race what you have left. A small negative split on trail beats a brave first half almost every time.
4. Print the splits. Wrist tattoo, watch screen, paper in a vest pocket. If you only see the splits inside an app, you will not look at them when it matters. Decisions made at the kitchen table hold up on a climb. Decisions made on the climb do not.

Where Trail Marathon Pacing Plans Go Wrong

Three errors come up in race reports more often than any other. They are all avoidable once you have done the maths above.

1. Pacing off the elevation profile alone. Two courses with identical 1,200 m of gain can finish 45 minutes apart depending on whether that gain comes in two big climbs or twenty rolling ones. Spread-out gain is cheaper to run than concentrated gain because you can keep running form for longer. Read the segment splits in old race results, not just the topo line.
2. Ignoring the descents. Steep downhills past about -10% gradient cost you more than gentle ones save. Quad damage compounds. A runner who flies down a 12% descent at 4:30 per kilometre in the first 15 km is the same runner who jogs the last 5 km at 7:00 per kilometre because their quads will not absorb landings any more.
3. Treating aid stations as zero-cost. Two minutes feels small until you have stopped at six of them. Plan the refills, count them in, and decide in advance which stations you skip and which you double up at.

For a wider read on how environmental conditions push pace around on race day, see the full breakdown in heat and pace – the heat penalty applies on trail too, and it stacks on top of every adjustment above.

Trail Marathon Kit That Actually Affects Your Pace

Most trail kit is comfort. A handful of items genuinely change your pace because they let you hold form on terrain where road kit cannot. Five pieces matter more than the rest.

• Trail running shoes with the right outsole. Road shoes on wet roots cost more time than any pacing error. A pair of trail running shoes with an aggressive lug pattern keeps your foot under your hip on climbs and descents, which is the only way the maths above holds up.
• Hydration vest with bottle pockets. A trail running hydration vest with two front bottle pockets and a 1 to 2 litre rear reservoir lets you drink while moving instead of stopping at every stream or station. That saves the minutes your non-running allowance is meant to cover.
• Collapsible running poles. On courses with sustained climbs above 12%, collapsible running poles shift load to the upper body and protect quads for the descent. Vernillo and colleagues note pole use reduces lower-limb load on climbs by a measurable margin. Worth their weight on any race with more than 1,000 m of gain.
• Trail gaiters. Stopping mid-climb to empty grit from a shoe is two minutes you did not plan for. Lightweight trail running gaiters cost almost nothing and remove the stop entirely.
• GPS watch with grade-adjusted pace and elevation profile. A watch that shows current gradient, GAP and remaining climb lets you pace by data rather than guess. A modern trail running GPS watch with a course load and real-time GAP is the difference between racing the plan and racing the feeling.

Common Questions About Pacing a Trail Marathon

How do you pace a trail marathon?

Start with your flat road marathon pace, then layer three adjustments on top: an elevation cost (roughly 60 seconds per 100 m of total gain), a terrain multiplier (5% to 30% on top of post-elevation pace depending on technicality), and a non-running allowance (about 2 minutes per aid station plus hike-walks on steep climbs). Split the adjusted target into three blocks and run the first third 5 to 10 seconds per kilometre slower than goal pace.

How much slower is a trail marathon than a road marathon?

Most trail marathons run 20% to 45% slower than the same runner’s flat road marathon, depending on elevation gain and terrain. A 3:45 road marathoner will typically finish a 1,200 m gain trail marathon on rolling singletrack between 4:30 and 4:45. Steep, technical courses with more than 2,000 m of gain can push the same runner past 5:30.

Should I run by heart rate or pace on a trail marathon?

Run by effort for the climbs, by adjusted pace on the runnable sections, and by feel on technical descents. Pace alone is useless on a steep climb because the number will look slow even at maximum sustainable effort. Heart rate alone is useless on technical ground because cardiac drift, surge response and the cost of micro-adjustments push it around unpredictably. Carry your adjusted splits but be willing to leave them on the climbs.

How do you calculate trail running pace?

Take your flat marathon pace from a road pace calculator, then add an elevation cost of roughly 60 seconds per 100 m of total gain across the course, a terrain multiplier of 5% to 30% on top, and a non-running allowance for aid stations and hike-walks. The result is an adjusted target time you can divide by the race distance to get your per-kilometre goal pace.

What is a good trail marathon time?

There is no single answer because terrain rewrites the scale. On a runnable course with under 600 m of gain, anything inside 4:30 is a strong recreational time. On a mountain course with 2,000 m of gain or more, a 6:00 finish often outperforms a 3:30 road runner. The cleanest benchmark is your own adjusted target, calculated from your current flat fitness and the course profile, not a generic time.

A trail marathon does not care what your road pace is. It cares whether you turned that pace into an honest plan. Do the maths the day you sign up, refine it the week you train on the course, and lock the splits in before race morning. A trail-specific training plan built around the demands of the course will get you to the start line in shape. The pacing plan above will get you across the finish line inside it.

This article is for informational purposes only and does not constitute medical advice. Trail running carries inherent risks including falls, exposure and altitude effects. If you are new to trail running, have a heart condition, or are planning a race at significant elevation, consult a qualified medical professional and build experience progressively before targeting a trail marathon.