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.
| Terrain | Gain per mile | Gain per km | Time cost on a loop course |
|---|---|---|---|
| Flat | 0-10 ft | 0-1.9 m | Under 1 sec/mile (under 25 sec over a marathon) |
| Moderately rolling | 10-50 ft | 1.9-9.5 m | 1-5 sec/mile (about 0.5-2 min over a marathon) |
| Rolling | 50-150 ft | 9.5-28 m | 5-14 sec/mile (about 2-6 min over a marathon) |
| Very hilly | 150-250 ft | 28-47 m | 14-23 sec/mile (about 6-10 min over a marathon) |
| Mountainous | 250 ft and up | 47 m and up | 23+ 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.