Why does the calculator use 12 seconds per mile per 100 feet?

This is the lower bound of the 12–15 s/mile range cited in coaching literature by Pete Pfitzinger and Jack Daniels. The range reflects average runners on moderate grades; faster athletes and steeper terrain often push toward the upper end. This tool uses the conservative 12 s/mile figure to avoid over-penalising pace.

Does this account for downhill sections?

No. The calculator applies a time penalty for elevation gain only. Downhills typically allow faster-than-flat pacing, but the magnitude depends on grade steepness, surface, and runner skill. Net elevation gain is the only vertical input here, so routes with significant descent are not fully modelled.

How accurate is this for trail ultras or mountain races?

Accuracy decreases on steep, technical terrain. The 12 s/mile heuristic was developed for road and rolling trail conditions (2–8 % grades). Grades above 10 % and technical features like scrambling or loose scree impose additional costs not captured by this linear model. Many ultra calculators layer separate rules for steep grades.

Can I use this to set training paces?

The output is an estimate, not a prescription. Many runners use adjusted pace as a planning reference for hilly courses, but individual hill-running efficiency varies. GPS watches and power meters provide direct feedback during sessions. This calculator offers a numerical starting point for exploration.

What if my base pace changes with fatigue on long runs?

The tool assumes a constant base pace throughout the run. In reality, pace often drifts on longer efforts due to glycogen depletion, heat, or cumulative fatigue. The calculation reflects a snapshot adjustment for elevation only; time-varying physiology is not modelled.

Running

Elevation-Adjusted Pace Calculator

Estimate time cost of vertical gain using the 12 s/mile per 100 ft coaching heuristic.

Last updated: 22 April 2026

What this tool does

This calculator estimates elevation-adjusted running pace by applying the Pfitzinger-Daniels coaching heuristic of approximately 12 seconds per mile per 100 feet of elevation gain. It accepts base flat-ground pace, total elevation gain in metres, and distance in kilometres, then outputs an adjusted pace per kilometre that accounts for the time cost of vertical ascent. The heuristic is a population-average rule of thumb used in endurance coaching and may not reflect individual climbing efficiency or terrain variability.

Inputs

Result

—

Formula Used

p_{a d j} = p_{ba se} + 0.245 \times E_{m}, (per-km adjustment; 0.245 s/km per m of gain)

p_{ba se}

Base pace in sec/km

E

Elevation gain in metres

d

Distance in km

Spotted something off? Let us know — we update calculators regularly.

How Elevation-Adjusted Pace Calculator works

The Elevation-Adjusted Pace Calculator estimates the time cost of vertical climbing during runs by applying a widely used coaching heuristic: approximately 12 seconds per mile per 100 feet of elevation gain. This tool converts that rule—derived from work by coaches Pete Pfitzinger and Jack Daniels—into metric units and distributes the penalty across your total distance. It takes your flat-ground base pace, the total elevation gain on a route, and the distance, then outputs an adjusted per-kilometre pace that reflects the additional effort required to climb.

The formula

The calculator uses the following conversion chain:

Start with ~12 seconds per mile per 100 feet of gain.
Convert to metric: 12 s/mile ≈ 7.46 s/km per 30.48 m of gain.
Per metre of gain: 7.46 / 30.48 ≈ 0.245 s/km.
Total time penalty = elevation_gain_m × 0.245 × distance_km seconds.
Adjusted pace = (base_pace_sec_per_km × distance_km + penalty) / distance_km.

The heuristic assumes consistent moderate gradients distributed across the run. The code applies the lower bound of the 12–15 s/mile range to remain conservative.

Where this method is most accurate

This approach works best on rolling terrain with moderate, sustained grades (2–8 %) found on road races or groomed trails. It fits well for events like half-marathons or marathons with net elevation profiles of a few hundred metres. The approximation degrades on very steep climbs (>10 %), where mechanical efficiency and gait changes compound the effect, and on technical single-track, where footing and cornering dominate pace. The tool does not account for downhill sections, which typically confer a time advantage; net gain is the only input. Altitude and weather effects are also excluded.

What this tool does not do

This calculator does not model downhills, variable-grade profiles, or technical terrain features like mud, roots, or rocks. It does not predict race outcomes, prescribe training paces, or incorporate individual physiological adaptation to hills. The output is an arithmetic estimate based on a single empirical rule, not a personalised prediction. It is not a substitute for training data, GPS watch metrics, or race-day experience.

Disclaimer

This tool provides educational estimates for reference only. It is not medical, training, or health advice and does not diagnose, treat, or prevent any condition. The calculations are approximations derived from published coaching heuristics and may not reflect individual performance. Users remain responsible for their own training decisions and safety. Consult a qualified coach or healthcare provider for personalised guidance.

Questions

Why does the calculator use 12 seconds per mile per 100 feet?: This is the lower bound of the 12–15 s/mile range cited in coaching literature by Pete Pfitzinger and Jack Daniels. The range reflects average runners on moderate grades; faster athletes and steeper terrain often push toward the upper end. This tool uses the conservative 12 s/mile figure to avoid over-penalising pace.
Does this account for downhill sections?: No. The calculator applies a time penalty for elevation gain only. Downhills typically allow faster-than-flat pacing, but the magnitude depends on grade steepness, surface, and runner skill. Net elevation gain is the only vertical input here, so routes with significant descent are not fully modelled.
How accurate is this for trail ultras or mountain races?: Accuracy decreases on steep, technical terrain. The 12 s/mile heuristic was developed for road and rolling trail conditions (2–8 % grades). Grades above 10 % and technical features like scrambling or loose scree impose additional costs not captured by this linear model. Many ultra calculators layer separate rules for steep grades.
Can I use this to set training paces?: The output is an estimate, not a prescription. Many runners use adjusted pace as a planning reference for hilly courses, but individual hill-running efficiency varies. GPS watches and power meters provide direct feedback during sessions. This calculator offers a numerical starting point for exploration.
What if my base pace changes with fatigue on long runs?: The tool assumes a constant base pace throughout the run. In reality, pace often drifts on longer efforts due to glycogen depletion, heat, or cumulative fatigue. The calculation reflects a snapshot adjustment for elevation only; time-varying physiology is not modelled.

Sources & Methodology

Applies the Pfitzinger/Daniels coaching heuristic of ~12 seconds per mile per 100 feet of elevation gain, converted to 0.245 s/km per metre of gain. Total penalty (elevation_gain_m × 0.245 × distance_km) is added to base time, then divided by distance to yield adjusted pace.

More in Running

View all 15 →