Elevation Gain/Loss Impact Calculator

Elevation Gain/Loss Impact Calculator

How much will hills slow you down? Enter elevation gain, loss, and distance to see adjusted pace, difficulty score, and equivalent flat distance.

:

How the Elevation Impact Calculator Works

Use the result as a rough course comparison, not a race-time promise. The calculator adds 60 seconds per 100m climbed and initially subtracts 30 seconds per 100m descended. These are fixed assumptions in this tool, not coefficients established by the original hiking rule or by Minetti’s laboratory study.

The descent calculation uses total loss divided by the entire course distance as a slope proxy. Above 10% it reduces the time saving; above 15% it adds time. It cannot see how steep any individual descent is. Two courses with the same distance, gain and loss receive the same time estimate even if one has short, steep hills and the other long, gradual slopes.

Road uses the resulting time adjustment unchanged; mixed terrain multiplies it by 1.07 and trail by 1.15. These are model settings, not measured penalties for every surface. The equivalent flat distance is calculated separately: course distance + 0.8km per 100m gained + 0.2km per 100m lost. Neither output accounts for your downhill skill, weather or fatigue.

For individual slopes, use the Grade Adjusted Pace (GAP) estimator. A whole-course estimate from total climbing cannot reproduce a segment-by-segment analysis. It also does not calculate how many gels or how much water you need.

The breakdown also shows km-effort: distance in kilometres plus one kilometre for every 100m climbed. For example, 45km with 1,500m of gain is 60 km-effort (ITRA runner FAQ). This climbing-based classification differs from this tool’s equivalent flat distance, which also weights descent.

The Science of Running on Grades

Minetti et al. (2002) measured energy cost on a treadmill at different gradients. Running cost was lowest at a −20% gradient in their experiment; the −10% minimum applied to walking. This is a laboratory energy-cost result, not advice to seek steep descents. It does not measure outdoor footing, injury risk or the fastest safe race pace.

Gaining height increases gravitational potential energy by approximately 9.8 joules per kilogram per metre. For a 70 kg runner climbing 100 m, that is 68.6 kJ of mechanical work. Converting this to metabolic energy or an equivalent flat distance requires additional assumptions; this number alone does not determine either.

Downhill running changes the muscular demand even when metabolic cost is lower. Eston et al. (1995) reviewed the role of eccentric muscle action during descent and its relationship to muscle damage. This review does not establish one fixed soreness peak or percentage loss of force for every downhill run. Do not equate lower oxygen cost with an easier muscular workload.

How Major Marathons Compare: Gain per Kilometer

Use these reference points to interpret the results you get from the calculator above. Gain per kilometer is a more honest difficulty metric than total climbing, because a 500 m spread across 42 km feels very different from 500 m piled into two Heartbreak Hills. Figures below are from findmymarathon course-profile data:

  • Berlin ~1.7 m/km gain (73 m total) — a relatively flat reference course.
  • Chicago ~1.8 m/km (74 m total) — flat lake-level loop; ideal for a flat PR attempt.
  • London ~3.0 m/km (127 m total) — mostly flat with subtle Thames-side rollers.
  • Tokyo ~1.4 m/km (60 m total) — flat with gentle rises; net downhill across 42 km.
  • Boston ~5.9 m/km gain, 9.2 m/km loss (248 m gain / 388 m loss) — a net-downhill course with early descents and the later Newton Hills.
  • NYC ~7.0 m/km (294m gain / 292m loss; FindMyMarathon profile checked 28 October 2026) — five bridges, including the Verrazzano climb out of the gate.
  • Big Sur ~12-16 m/km (504-665 m total depending on source: 665 m per the official bigsurmarathon.org course PDF; 504 m per findmymarathon) — scenic California coast; with 504–665m of reported climbing and Hurricane Point at mile 10-12.

Use these figures to compare climbing density, not to assign a guaranteed time penalty. At 6m/km, a marathon has about 253m of gain. If it has the same amount of descent, this tool adds about 76 seconds on the road setting; that model result does not establish how much slower you personally will race.

How Hilly Is Hilly? Gain per Mile and per Kilometer

Runners disagree about whether a course is “hilly” because this page uses a broad set of terrain bands, from road races to mountain courses. In these bands, every World Marathon Major lands in the bottom two bands — Boston sits near 31 ft per mile and New York near 37 ft per mile, which is only “moderately rolling,” and Big Sur, at 63-84 ft per mile, still lands mid-“rolling.” If your race felt brutal but scores low here, that is the scale doing its job: it has to stretch all the way to alpine ultras.

TerrainGain per mileGain per kmTime cost on a loop course
Flat0-10 ft0-1.9 mUnder 1 sec/mile (under 25 sec over a marathon)
Moderately rolling10-50 ft1.9-9.5 m1-5 sec/mile (about 0.5-2 min over a marathon)
Rolling50-150 ft9.5-28 m5-14 sec/mile (about 2-6 min over a marathon)
Very hilly150-250 ft28-47 m14-23 sec/mile (about 6-10 min over a marathon)
Mountainous250 ft and up47 m and up23+ sec/mile (10 min and up)

The time column assumes a loop or out-and-back where gain equals loss, using the same coefficients as the calculator above: 60 seconds added per 100 m climbed, 30 seconds returned per 100 m descended. Because the descent refunds only half of what the climb costs, a course that finishes where it started still costs you time — roughly 30 seconds per 100 m of gain. The model gives the same result for one climb or forty rollers because it does not read the individual slopes. Point-to-point courses have unequal gain and loss, so enter both numbers in the form above to see yours.

To place your own race, take the total gain from the official course page, divide by the race distance, and read across. A marathon with 300 m of gain is 7.1 m/km, or 38 ft per mile: moderately rolling in this table, with a model adjustment of about 90 seconds on the road setting. One caveat — this scale cannot separate road marathons from each other, because they all compress into the bottom two bands. For road-versus-road comparison use the per-kilometer figures in the table above this one, and read the calculator’s 1-10 difficulty score the same way: it spans city road to alpine ultra, so a road marathon scoring 1-2 is normal, not an error.

Pacing Strategy for Hilly Courses

Read the course profile before turning the average adjusted pace into a pacing plan. Mark where the climbs and descents occur. A single average cannot tell you how fast to run each kilometre.

Use a familiar hilly training route to check how your effort and pace change on climbs. Do not force a universal uphill cadence percentage or a fixed number of seconds per kilometre: neither is calculated from your inputs. On descents, practise at a pace you can control rather than treating the model’s time saving as time you must win back.

For a steep section, compare walking and running in training before deciding how to tackle it on race day. This tool cannot identify a personal gradient where walking becomes more efficient. Use the GAP calculator for individual gradients and the finish time calculator to translate a chosen average pace into a finish time.

Frequently Asked Questions

How much does elevation gain affect marathon time?

In this model, each 100m climbed adds 60 seconds before descent and terrain adjustments. That is a calculator assumption, not a universal time penalty. With 500m of gain and no descent on the road setting, it adds 5 minutes. With 500m of gain and 500m of descent, it adds about 2.5 minutes.

Actual race performance also depends on the individual slopes and the runner. This tool only takes totals, so it cannot distinguish one long climb from many short ones with the same total gain.

What is Grade Adjusted Pace (GAP) and how is it calculated?

Grade Adjusted Pace (GAP) expresses the flat-ground pace corresponding to an estimated effort on a slope. It depends on the model used. Minetti et al. (2002) measured energy cost across treadmill gradients; their study is useful background, but it did not validate this calculator’s fixed seconds-per-100m coefficients.

This tool estimates an average pace from total gain, loss and distance. For an individual slope, use the linked GAP tool; total climbing alone cannot reconstruct a course’s changing gradients.

Does running downhill make up for the time lost going uphill?

Not fully in this model. At its moderate descent setting, 100m down saves 30 seconds while 100m up costs 60 seconds. A road loop with 300m gained and lost therefore adds about 90 seconds.

The descent setting is based on total loss divided by total course distance, not the slope of each downhill. Do not read its 10% and 15% cutoffs as measurements of your course’s steepest descent or as universal limits on downhill running.

What is equivalent flat distance, and why does it matter for fueling?

Here, equivalent flat distance is a model comparison number, not a measurement of calories or fluid loss. The formula adds 0.8km per 100m climbed and 0.2km per 100m descended. A 42.2km course with 500m of gain and 500m of loss gives 47.2km; with no descent, it gives 46.2km.

It does not follow that you need food or water for exactly that many flat kilometres, or that you will run out of fuel at a particular marker. Make a separate fueling plan for the expected duration using an approach you have practised. The calculator does not take carbohydrate intake, sweat loss or fluid intake as inputs.

How does terrain type change the elevation penalty?

Road uses 1.00, mixed terrain 1.07 and trail 1.15 as multipliers on the net elevation time adjustment. For example, a 100-second net adjustment becomes 115 seconds on the trail setting. The multiplier does not apply to the entire flat finish time or to equivalent flat distance.

These are fixed settings in this calculator, not measured penalties for every trail. Rocks, mud and technical descents are not separate inputs, so the result cannot tell you the specific cost of those conditions.

What does the 1-10 course difficulty score mean?

The score spans a flat city marathon to an alpine ultra, so road marathons cluster at the very bottom — which surprises most people. Feeding real course data into the calculator: Berlin, Tokyo, London, New York and Boston all score 1.2-2.0; Big Sur, with 504-665 m of climbing, reaches 2.7-3.7; a trail marathon with 1,000 m of gain scores 5.8; a 50K with 2,500 m maxes the scale at 10. The formula is driven by gain per kilometer — the reference road races here have much less climbing per kilometre than UTMB 2026, whose published 9,700m over 174km works out to about 56m/km — then adds up to 1 point for trail terrain and up to 1 point for very high total elevation change.

So read the score as “where does this rank among everything I could run,” not “is this harder than my last road marathon.” For road-versus-road, compare gain per kilometer instead: going from Berlin (1.7 m/km) to Boston (5.9 m/km) moves the difficulty score by only 0.6, but the score does not calculate a personal race-time buffer. Use gain per kilometre to compare the climbing and inspect the actual profile before choosing a goal time.

How much harder is Boston Marathon because of elevation?

With the reference values on this page—248m gained and 388m lost—the road model adds about 32 seconds. The arithmetic is 148.8 seconds added for climbing minus 116.4 seconds saved on descent. This does not mean Boston is only 32 seconds harder than a flat marathon.

The totals hide where the hills occur. Check the early descents and later Newton Hills in the course profile and compare them with your training. This calculator does not model fatigue from those sections and does not calculate a personal race-time penalty for them.

How do I find accurate elevation data for a course?

Start with the organizer’s current course map or published gain and loss. Check the edition and the route before copying a figure from a previous year. If only a GPX file is available, inspect it in a route tool and note which service produced the elevation estimate.

Different devices and mapping services can give different totals because their elevation sources and smoothing differ. Keep the source consistent when comparing courses; do not assume a prior finisher’s GPS track is automatically accurate or rank every barometric estimate above every map-based one.

Should I walk the hills in a marathon or trail race?

Decide from the actual hill and your training, not a universal 15% cutoff. The calculator has no input for your walking speed, running economy or the grade of each climb, so it cannot identify where walking is the better option for you.

On a similar slope in training, compare the time and effort of walking and running before choosing a race strategy. Include the walking time when estimating total duration; equivalent flat distance alone does not determine a fueling plan.

Does elevation gain include downhill?

No. Cumulative elevation gain adds up only the climbs; descents are tracked separately as elevation loss and are never subtracted. A route that climbs 300 m, drops 100 m, then climbs another 200 m has 500 m of gain and 100 m of loss — not 400 m. That is exactly why this calculator asks for gain and loss as two separate inputs: they move your finish time in opposite directions and by different amounts (60 sec added per 100 m up, only 30 sec returned per 100 m down).

Watch and mapping-service totals can differ because of elevation sources and smoothing. Before comparing two runs, check how both totals were produced rather than assuming the larger number is more accurate.

References 3 sources
  1. Naismith, W.W. (1892). Excursions: Cruach Ardran, Stobinian, and Ben More. Scottish Mountaineering Club Journal.
  2. Minetti, A.E., Moia, C., Roi, G.S., Susta, D., & Ferretti, G. (2002). Energy Cost of Walking and Running at Extreme Uphill and Downhill Slopes. Journal of Applied Physiology. doi:10.1152/japplphysiol.01177.2001
  3. Eston, R.G., Mickleborough, J., & Baltzopoulos, V. (1995). Eccentric Activation and Muscle Damage: Biomechanical and Physiological Considerations during Downhill Running. British Journal of Sports Medicine. doi:10.1136/bjsm.29.2.89