Altitude Adjusted Pace Calculator

The Altitude Adjusted Pace Calculator shows how much a given elevation will slow the pace you normally hold at sea level. Enter your pace per mile or kilometer and the altitude of the race or camp — meters or feet, up to 5,000 m — and it returns the adjusted pace plus the percentage penalty. The model tracks how VO₂ max falls in thinner air, which is why a relaxed sea-level effort feels labored in Denver or Flagstaff. Racing somewhere hot as well as high? Stack this with a heat-adjusted pace estimate.

Your sea-level paceWhere you are running
Pace at altitude5:14 /km
Sea-level pace5:00 /km
VO₂ max loss4.7%
Altitude2000 m
ConditionsHigh altitude — ease pace and allow time to acclimatise

5 /km · 0 · 2000 m

How it works

pace at altitude = sea-level pace × (1 + VO₂max loss)

Two constants drive the whole calculation. Below 1500 m an unacclimatized runner gives up about 1% of pace per 1000 m of elevation; above 1500 m the cost steepens to roughly 6.3% per additional 1000 m (Péronnet, Thibault & Cousineau, 1991; Wehrlin & Hallén, 2006). Concretely, the loss fraction is 0.01 × (altitude ÷ 1000) up to the 1500 m break point, and 0.015 + 0.063 × ((altitude − 1500) ÷ 1000) beyond it. Run the numbers for 2000 m and the penalty comes to 4.65%, turning a 5:00/km sea-level pace into roughly 5:14/km. Mile-high cities cost around 2%, while races between 2000 and 3000 m take 6–12% off an unadapted runner. Here is the two-phase model tabulated at round elevations: | Elevation | Model phase | Slowdown | | --- | --- | --- | | 500 m | ~1%/1000 m | 0.50% | | 1000 m | ~1%/1000 m | 1.00% | | 1500 m | break point | 1.50% | | 2000 m | ~6.3%/1000 m | 4.65% | | 2500 m | ~6.3%/1000 m | 7.80% | | 3000 m | ~6.3%/1000 m | 10.95% | And the same constants applied to venues US runners actually race at: | Location | Elevation | Penalty | | --- | --- | --- | | Denver, CO | 1609 m | 2.2% | | Albuquerque, NM | 1619 m | 2.2% | | Boulder, CO | 1655 m | 2.5% | | Mexico City | 2240 m | 6.2% | | Leadville, CO | 3094 m | 11.5% | All of these figures assume you arrive unadapted. Give the body one to three weeks at elevation and red-cell mass and oxygen delivery improve, shrinking — though rarely erasing — the gap. Terrain stacks on top of thin air: on a hilly mountain course, correct for the climbing separately, and when heat compounds the elevation, add a heat adjustment on top. Responses to altitude differ a lot between runners, so read the output as a planning band rather than a fixed number.

Sources

FAQ

How much will altitude slow my running pace?

Modestly below 1500 m — about 1% per 1000 m of elevation — and much more above that, roughly 6.3% per extra 1000 m. An unacclimatized runner racing at 2500–3000 m can expect to give up 6–10%. Enter your own pace and elevation to see the exact figure the model produces.

What does the model say about running in Denver?

Denver is at 1609 m — 5280 ft, the mile-high mark — where the penalty works out to about 2.2%. That nudges a 5:00/km runner to roughly 5:07/km and stretches a 40:00 10K to about 40:53. Noticeable in a race, but far gentler than at true high-altitude venues.

How much time does altitude add to a marathon?

Scale the sea-level finish by the penalty for that elevation. A 4:00:00 marathoner loses about 5 minutes at a mile-high venue (~2%), finishing near 4:05, and about 15 minutes at Mexico City elevation (2240 m, ~6.2%), finishing near 4:15 — hills and heat not included. Acclimatization claws part of that back.

At what elevation does the slowdown really kick in?

There is no free zone — even 500 m costs half a percent — but 1500 m is the turning point. Below it the loss creeps along at about 1% per 1000 m; above it the rate jumps to roughly 6.3% per 1000 m, which is why events near 2000 m and beyond feel like a different sport.

Why does thin air hit distance runners so hard?

Endurance pace is capped by how much oxygen your muscles can process, and that ceiling — VO₂ max — drops as the air thins. Sprints, which run on stored energy, barely suffer; a 10K or marathon, which runs on oxygen, slows nearly in step with the VO₂ max loss.

Does the penalty shrink once I acclimatize?

Partly. After one to three weeks at elevation the body builds more red blood cells and moves oxygen more efficiently, so the gap narrows without fully closing for most runners. The calculator models the fresh-off-the-plane case, so treat its output as your first-week worst case.

Can I enter pace per mile and altitude in feet?

Yes — the pace field toggles between /mi and /km, and the altitude field accepts meters or feet up to 5,000 m (about 16,400 ft). Everything is converted internally before the percentage is applied, so both unit combinations return the same adjusted pace.

Should I read the result differently for a race versus a training camp?

For a race, treat the adjusted pace as your realistic target from the gun — going out at sea-level pace at 1,800 m is how the last 10K falls apart. For a camp, it is your week-one guide: hold the adjusted effort early, then re-run the number as acclimatization builds and the real-world gap narrows.

Do I get a boost when I come back down to sea level?

The calculator only models the penalty of thin air — it never outputs a faster-than-baseline pace. Runners returning from several weeks up high often do race well at sea level thanks to the extra red blood cells built there, but that effect varies too much between individuals for a formula to promise it.

The adjustment reflects a population-average VO₂ max model for unacclimatized runners; your personal response may be larger or smaller. Altitude sickness is a genuine hazard at higher elevations — ascend progressively and get medical guidance for high destinations. Planning information only, not medical advice.

Embed this calculator

Add the altitude adjusted pace calculator to your website or club page — free, no sign-up. Paste this snippet where you want the calculator to appear:

<script src="https://pacerrunning.net/embed/altitude-adjusted-pace-calculator.js" async></script>