Altitude Pace Adjustment
Estimate how much slower your running pace will be at elevation compared to sea level. Use this before racing or training at altitude to set realistic effort targets and avoid blowing up early.
Last updated: September 2026
Adjusted Pace
5.15 min/km
Formula below · 1 source (doi.org) · Updated Sep 2026
Compare with similar
About this calculator
At altitude, reduced atmospheric pressure means less oxygen is available per breath, forcing the cardiovascular system to work harder to sustain the same pace as at sea level. This calculator estimates your adjusted pace using: adjustedPace = seaLevelPace × (1 + altitude × 0.00002), where seaLevelPace is in min/km and altitude is in metres. The factor 0.00002 per metre is a flat 2% pace slowdown per 1,000 m, counted from sea level. Real losses vary: in trained endurance athletes Wehrlin & Hallén (2006) measured VO2max falling about 6% per 1,000 m from near sea level, but race times slow less than VO2max falls, and modelling by Péronnet et al. (1991) shows the penalty growing faster at higher altitude while sprints are barely affected. Treat the straight 2% per 1,000 m as an estimate and pace by effort. The effect is most pronounced for events lasting more than a few minutes, where aerobic metabolism dominates. Acclimatisation over days to weeks can partially but not fully offset it. The pace is shown in decimal minutes per km: multiply the decimal part by 60 for seconds, so the default 5.15 min/km is 5:09 per km.
How to use
You normally run at 5:00 min/km at sea level and plan to race at 2,500 m altitude in Bogotá. Step 1: Enter seaLevelPace = 5.0, altitude = 2500. Step 2: Apply the formula: adjustedPace = 5.0 × (1 + 2500 × 0.00002) = 5.0 × (1 + 0.05) = 5.0 × 1.05 = 5.25 min/km. Step 3: 0.25 min × 60 = 15 s, so your adjusted target pace is 5:15 per km. Starting at your sea-level pace at this altitude will feel much harder — planning for 5:15 min/km protects you from going out too fast.
Frequently asked questions
How much does altitude affect running pace and performance?
The effect grows with elevation and varies between runners. Trained athletes lose roughly 6% of VO2max per 1,000 m (Wehrlin & Hallén, 2006), but race pace slows less than that because they run below VO2max, and the slowdown steepens at higher altitudes. This calculator simplifies that to a flat 2% per 1,000 m from sea level, so at 3,000 m it adds 6%: a sea-level 40-minute 10K runner would run about 42:24. The impact is greater for longer events where aerobic capacity is the primary limiter, and smaller for short sprints powered mostly by anaerobic metabolism. Individual variance is also significant — some runners are more altitude-sensitive than others.
How long does it take to acclimatise to running at altitude?
Initial acute acclimatisation — increased breathing rate and heart rate stabilising somewhat — begins within the first 24–48 hours. Meaningful physiological adaptation, including increased red blood cell production, takes 2–3 weeks of consistent exposure at altitude. A common coaching recommendation is either to arrive less than 24 hours before competition or to stay long enough (about 2–3 weeks or more) for real adaptation; this is practical advice rather than a firm research rule.
Should I adjust my training effort or training pace when running at altitude?
Most coaches recommend adjusting effort (perceived exertion or heart rate) rather than rigidly maintaining your sea-level pace targets. Attempting sea-level paces at altitude leads to excessive physiological stress, poor recovery, and higher injury risk. Use this calculator to estimate equivalent adjusted paces, then treat those targets as your new benchmarks for the duration of your altitude stay. Heart rate monitors are especially useful at altitude because they reveal how hard your body is actually working even when pace looks modest.
Related calculators
Sources & references
Think a result is wrong? Report a problem with this calculator.