What Does GAP Mean in Running? Grade-Adjusted Pace Explained (Strava & Garmin)

GAP stands for grade-adjusted pace: your running pace converted into the flat-ground pace that would cost the same effort. Run 14:00/mile up a 12% climb and your GAP might be around 9:00/mile - that is the number your legs and heart rate actually feel. Raw pace lies on hills; GAP translates every slope onto equal, flat terms. You can compute it for any pace and gradient with our free GAP calculator.

What does GAP mean on Strava?

On Strava, GAP is the estimated pace you could have held on flat ground for the same effort - shown next to your raw pace on every split of a hilly run. Strava computes it from the gradient of each segment of your activity, using an effort model originally calibrated on heart-rate data from millions of runs. Uphill splits get a faster GAP than raw pace; gentle downhill splits get a slower GAP, because gravity did part of the work.

Garmin shows the same idea on compatible watches and in Garmin Connect, where it is also labelled grade-adjusted pace. The exact numbers differ slightly between platforms because each uses its own cost model, but they agree on the principle and rarely disagree by more than a few seconds per kilometre on moderate slopes.

Average GAP vs average pace

Average pace is distance divided by time - it treats a mountain run like a track session. Average GAP re-weights every section of the run by its gradient first, then averages. The two diverge as soon as the route is hilly:

• On a loop or out-and-back with balanced climbing and descending, average GAP is usually a bit faster than average pace, because the time lost climbing is bigger than the time gained descending.
• On a net-uphill run, average GAP can be dramatically faster than raw pace - a 7:00/km average on a steady 8% climb is a strong effort, and GAP will say so.
• On a net-downhill run, average GAP is slower than raw pace: the clock flattered you.

That is why average GAP, not average pace, is the number to compare across different routes - it answers “how hard did I actually run?” rather than “how fast did the ground let me go?”.

Compare GAP, not pace: it tells you how hard you ran, not how fast the ground let you go.

How is GAP calculated?

The energy-cost curve

GAP is built on the energy cost of running at a gradient. The classic reference is Minetti’s laboratory work measuring how many joules per kilogram per metre it takes to run up and down slopes of varying steepness - the Minetti energy-cost curve. The curve is not symmetric: cost climbs steeply with positive gradient, and going down is cheap only for a while. Strava’s model refines the same shape with heart-rate data from real-world runs rather than treadmill measurements.

Our GAP calculator applies that cost model to your pace and a given gradient, returning the equivalent flat pace. Feed it a 12% climb at 14:00/mile and it will tell you that effort is closer to a 9:00/mile on the flat - which is why your heart rate agreed with the effort, not the watch.

Why descents are different

The asymmetry matters most in descents. Running downhill is metabolically cheaper than the flat only up to about -10% to -15%. Beyond that, the cost rises again, because you are braking hard with every step. That eccentric braking load is what shreds your quads at hour eight of an ultra, even though your pace looks fast. A steep descent is simultaneously faster on the clock and more damaging to your legs than a moderate one.

Is GAP accurate on trails?

GAP is a model, not a law - and on trails it comes with three caveats:

1. It assumes good footing. Technical terrain (rocks, roots, mud, scree) slows you down without showing up in the gradient, so GAP underestimates your effort on technical ground.
2. It ignores altitude and fatigue. The cost model is calibrated at low altitude on fresh legs; at 2,500m or at hour ten, the same GAP costs more.
3. It captures the metabolic cost of descents, not the muscular damage. GAP will happily rate a -18% bomb as easy; your quads will disagree late in the race - cap steep descents by judgement, not by GAP.

On smooth, runnable trails at moderate gradients, GAP tracks effort well and is the single most useful number for comparing hilly runs. Treat it as a way to normalise effort across a course, not as a promise of finish time.

Using GAP to pace a race

1. Find your sustainable flat effort. This is the GAP you can hold for the race distance, not your 5K pace.
2. Convert it to real paces per section. On the climbs your real pace will be much slower; on runnable descents, faster. Both can map to the same GAP.
3. Cap your descents. If GAP says you could run a -18% descent at a blistering flat-equivalent, hold back anyway.

Pair GAP with the incline calculator to turn a course profile into a segment-by-segment effort plan before race day.