Summit LineGet started free →

⏵ Free tool · No signup

Trail Run Time Calculator

Put in a distance, the total elevation gain, and the pace you hold on flat ground. You get back an estimated trail finish time and your effective trail pace, with the climbing already baked in, built on the same grade-adjusted pace math the Summit Line app runs on. A flat estimate tells you almost nothing about a mountain race. This one counts the vert.

⏵ YOUR RUN

DIAL IT IN

Distance
mi
Total elevation gain
ft

= 161 ft/mi of climbing

Your flat / road pace
min
:
sec

The pace you hold on flat ground or the road, per mile. This is your engine before the hills tax it.

⏵ YOUR ESTIMATE

WHAT THE CLIMB COSTS

Estimated time
4:54
Range 4:49 to 4:59
Trail pace
9:29/mi
Flat pace 9:00/mi
Slowdown
+5%
Pace cost of the vert
Added by hills
+0:29/mi
On top of flat pace

Why a range, not a single number

This estimate models the pace cost of average grade from your distance and total gain. It does not see technical footing, altitude, mud, or how the climb is distributed, all of which move the real number. Treat the midpoint as a target and the band as the realistic spread.

⏵ THE MODEL

HOW WE GOT THERE

  • Average climb per mile161 ft/mi
  • Pace added per mile by climb+0:29/mi
  • Grade penalty model~18 sec/mi per 100 ft/mi

We run the product grade model in reverse: it credits a flat equivalent to a real climb, so we add that same per mile cost back onto your flat pace. The penalty is capped so very steep, short inputs stay sane.

⏵ This is an average-grade estimate

Summit Line projects your finish on YOUR exact course profile, not a flat estimate. It reads the real elevation profile and your own pace-by-grade off your runs, then calls your splits climb by climb instead of smearing all the vert into one average.

Start free →See it on a real course

How the trail time estimate works

A trail mile and a road mile are not the same mile. The difference is the climbing, and this calculator takes your elevation gain and turns it into a real pace cost. Here is the thinking behind the numbers above.

Start from your flat pace, then add the climb cost

The honest way to estimate a trail finish is to start from a pace you actually know, the one you hold on the road or a flat path for a similar distance, and then add what the hills are going to cost you. That keeps your engine (your flat pace) separate from the terrain tax (the vert). It is how runners who have done a few of these think about pacing a hilly race.

This tool uses a grade penalty of roughly 18 seconds per mile for every 100 feet of climb per mile. So a course with 200 feet of gain per mile adds about 36 seconds per mile to your flat pace, and a nasty 400 feet per mile adds over a minute. The penalty gets capped at the steep end, because past a point you are hiking, not running, and a straight-line penalty would make the slowdown look worse than it is.

It is the same grade-adjusted pace math, run in reverse

Grade-adjusted pace usually answers a backward-looking question. You ran a hilly route, and GAP tells you the flat-ground pace that effort was worth. Summit Line works that out by putting a pace value on the average grade of a run, so a slow climb reads as a faster flat-equivalent effort.

This calculator runs that same relationship forward. Instead of giving a real climb its flat equivalent, it takes your flat pace and adds the same per-mile grade cost back on, and that gives you the trail pace you will actually run. Same model, just pointed the other way. That is why the estimate sits on the real product math and not some made-up number.

Why the answer is a range, not a single time

Two numbers, distance and total gain, cannot catch everything that decides a trail finish. Rocky footing, mud, snow, altitude, switchbacks, where the climb actually falls, time burned at aid stations, and how you come apart late in a long race all push the real time around. A model that ignores all of that and hands you one exact time is lying to you.

So the calculator gives you a band around the midpoint. Treat the midpoint as your target effort and the range as the spread you should actually expect. The more technical or the higher the course, the more you should lean toward the slow end of that band.

For a real projection, you need the whole profile

Average grade is only a first guess. A race that front-loads all its climbing paces completely differently from one that saves the big climb for mile 90, even when the total gain is exactly the same. Real pacing comes from the full elevation profile plus your own measured pace-by-grade, so the projection knows how fast you go up versus down at each gradient.

That is the difference between a free average-grade estimate and a projection built for your course. Summit Line builds the second one. It takes in the course profile, learns your pace-by-grade off your training, and calls your splits and finish climb by climb, then ties it to a fueling and pacing plan for race day.

Keep planning your race

⏵ Tool

Grade-Adjusted Pace Calculator

Turn a hilly run into its flat-equivalent pace, the math behind this estimate.

⏵ Tool

Race Time Calculator

Get a finish time from distance and goal pace for any race.

⏵ Tool

Race Equivalent Calculator

Take a result at one distance and see what it is worth at another.

⏵ Tool

Ultra Fueling Calculator

Carbs, sodium, and fluid per hour once you know how long you are out there.

⏵ Guide

How to train for elevation gain and vert

Build the climbing legs that shrink the pace penalty this tool puts on you.

⏵ Guide

How to pace an ultramarathon by effort

Why effort, not pace, is the lever you want on a course full of climbs.

⏵ Guide

How long does it take to run a 100 mile race

What total gain does to finish times across the 100 mile distance.

Trail run time FAQ

How long will a trail run take?

A trail run takes longer than the same distance on flat ground, and almost all of that comes down to elevation gain. Start with the pace you hold on the road or a flat path, then tack on a penalty for the climbing, roughly 18 seconds per mile for every 100 feet of climb per mile. Say you run 10 miles with 2,000 feet of gain (200 ft per mile). That adds about 36 seconds per mile, so a 9:00 road runner is closer to 9:36 per mile and finishes around 1 hour 36 minutes. Put your own numbers in above and you get an estimate scaled to your pace and your course.

How much does elevation gain slow you down?

A good rule of thumb: every 100 feet of climb per mile costs you about 18 seconds per mile on top of your flat pace. Spread that across a whole course and a hilly race with 200 to 300 feet of gain per mile can run 30 to 90 seconds per mile slower than the road. Steeper, rockier, or higher up and it costs you even more, because at some point you stop running the climbs and start hiking them. But the slowdown does not keep climbing forever, which is why this calculator caps the penalty so a short, brutally steep effort does not spit out nonsense.

How do I estimate a trail race finish time?

Three numbers get you a realistic estimate: the race distance, the total elevation gain (off the race website or a GPX of the course), and the pace you can hold on flat ground for that distance. Turn the gain into feet per mile, add the grade penalty to your flat pace, then multiply that trail pace by the distance. The calculator above does all of that for you, and it gives you a range instead of one number, because the real finish also hangs on footing, heat, altitude, and how the climb is spread out.

What is grade-adjusted pace?

Grade-adjusted pace (GAP) is the flat-ground pace that would have cost you the same effort as your actual hilly run. It lets you put a slow grind up a mountain and an easy cruise on the road on even footing. Climbing is expensive, so a 10:00 per mile slog uphill might be worth an 8:00 per mile flat effort. This calculator just runs that idea backward. It starts from your flat pace and adds the grade cost back on to figure out what you will really run on the trail.

Why is my trail pace so much slower than road?

Because climbing is work your road pace never has to do. Every foot of vertical is you lifting your own body weight, and on the steep stuff you go from running to hiking, which is way slower on the clock even when you are working hard. Now stack soft or rocky footing, switchbacks, altitude, and the fatigue that piles up, and a trail mile can run one to three minutes slower than your road mile. That gap is normal. It is not you losing fitness.

How accurate is a trail time estimate?

Treat it as a planning range, not a stopwatch. The model takes your distance and total gain and estimates the average pace cost of the grade, which is a solid first guess. What it cannot see from two numbers is the technical stuff, mud, snow, altitude, where exactly the climb falls, time standing around at aid stations, and how you fall apart late in a long race. That is why you get a band instead of a single time. For a real finish projection on your actual course, you need the full elevation profile and your own pace-by-grade data, and that is what Summit Line builds.

Go from an estimate to a course projection

Summit Line reads your real course profile and your own pace-by-grade, calls your splits and finish climb by climb, and ties it to a fueling and pacing plan you have actually rehearsed. Pace off your own runs, an AI race brief, and a finish you can trust.

Get started free →Explore the demo

This calculator estimates the pace cost of average grade from distance and total elevation gain. It does not account for technical footing, altitude, the help you get on descents, or where the climb falls, so treat the output as a planning range, not a guaranteed finish time. Always check it against your own efforts on similar terrain.