Garmin VO2 Max: How Accurate It Is, And Why It Falls When You Get Fitter
Condividi
Your Garmin has never measured your VO2 max.
A real VO2 max test involves a mask, a treadmill, an analyser measuring the oxygen you breathe in against the carbon dioxide you breathe out, and someone telling you to keep going until you cannot. Your watch has your pace, your heart rate, and a model that works backwards from the two.
That is not a criticism — the inference is clever and close enough to be useful. But it means the number is only ever as good as its inputs, which is why the most common complaint about it — "my VO2 max is going down while I am training well" — usually has nothing to do with your fitness.
What Garmin's estimate actually is
The logic: how fast you run at a given heart rate tells you something about your aerobic capacity. Holding 5:00 per kilometre at 70% of your maximum heart rate indicates a bigger engine than holding the same pace at 90%. Feed in enough of those pace-and-heart-rate pairs from a sustained run and you can extrapolate towards the pace at maximum effort, and from there to an oxygen uptake figure in millilitres per kilogram per minute.
For that to work, your watch needs a run it can actually read. On most Forerunner and Fenix models that means roughly ten minutes or more of steady outdoor running at a decent intensity, with GPS and heart rate. Which rules out a lot of your training:
- Treadmill runs generally do not qualify, because there is no GPS pace.
- Easy runs are often too gentle to produce a usable estimate.
- Short runs and interval sessions may not give a long enough steady block.
- Cycling gets its own separate VO2 max estimate, and on most models that one needs a power meter — heart rate alone is not enough on the bike.
Notice what those requirements have in common: they are about data quality, not about you.
Diagnosing a moving number
This is the part no other page gives you. Find your symptom in the left column.
| What you are seeing | Most likely cause | What to check |
|---|---|---|
| Drifting down over weeks while your training is going well | Your max heart rate is set too low, or auto-detect revised it downwards | The max HR value in your user profile. This is the big one |
| Dropped sharply straight after one run | Bad heart rate data on that run — an optical spike, a strap dropout, cadence lock | Open that activity and look at the heart rate trace for impossible jumps |
| Fell during hot or humid weather | Cardiac drift. Your heart rate is higher at the same pace, so you look less fit | Nothing. It usually recovers as you acclimatise or the weather cools |
| Fell after you moved to hills or trails | GPS pace does not account for gradient, so climbing looks like being slow at a high heart rate | Judge the estimate from flat road runs only |
| Fell after you changed devices or straps | Different heart rate hardware, different profile, or a reset max HR | Your profile fields and your max HR, straight after any device change |
| Has not moved in months despite consistent training | The ceiling effect — see below. For a trained runner this is normal, not a fault | Nothing. Track your threshold pace instead |
| No value at all, or badly out of date | No qualifying runs — all treadmill, all easy, all short, or no GPS | Do one flat outdoor run of 20–30 minutes at a firm, sustainable pace |
Why a wrong max heart rate is the usual culprit
Work through the arithmetic and it becomes obvious.
The estimate hinges on your heart rate relative to your maximum. Suppose your true maximum is 190, but your watch has 170 in the profile because it applied the 220-minus-age formula. You run a steady effort at 150 beats per minute. Against your true ceiling that is about 79% — comfortable, clearly sub-threshold work. Against the stored ceiling of 170 it is 88%, which the model reads as a hard effort.
Same run, same pace, same heart rate. But with the lower ceiling, the model concludes you needed to work much harder to hold that pace — so it reports a lower VO2 max. A max heart rate set too low systematically depresses your VO2 max estimate, permanently, with no warning.
It gets worse, because Garmin can revise your max heart rate downwards on its own if auto-detection is enabled and your highest readings are coming from an optical sensor that under-reads during hard efforts. That produces the classic pattern: a VO2 max that slides gently downwards for months while you are in the best shape of your life.
Two things make this especially sneaky. The first is that editing an unrelated profile field — your weight, your birth year — has been reported to reset a stored max heart rate back to the age-based default. The second is that nothing tells you it happened. How to find a max heart rate you can actually trust, and what else breaks when it is wrong — and it is not just VO2 max. Recovery time, training load, readiness and training status all move with it.
If your VO2 max is falling, check this before you change a single thing about your training.
So how accurate is it, really?
Three honest statements, in order of usefulness.
As a trend for one person, it is reasonable. Under good conditions — a chest strap, flat road running, a sensible max heart rate, consistent weather — the direction of travel over months is usually meaningful. That is the use it is fit for.
As an absolute number, treat it loosely. Firstbeat, the analytics company behind Garmin's estimate, has published accuracy claims for ideal laboratory-comparison conditions, and independent comparisons against real gas-exchange tests generally find the estimate in the right neighbourhood — but with enough individual variation that a single reading should not be taken as your number.
For comparing yourself with other people, it is close to worthless. Two runners showing the same figure can have very different real values, because they have different max heart rate settings, different sensor quality and different terrain. That is comparing two calculations, not two athletes.
What counts as a good VO2 max
The useful answer is "good compared with what?" — because an absolute number means little on its own. Garmin itself does not just show you the figure; it grades it against population norms for your age and your sex, and reports a fitness level band alongside it (the bands run from poor up to superior on most models). That comparison is far more informative than the raw number, and it is the one to pay attention to.
If you want rough orders of magnitude anyway, the broad picture across the adult population looks something like this:
- Sedentary adults commonly sit in the twenties and thirties.
- Regularly active people who do not race tend to land in the high thirties and forties.
- Committed recreational runners are often in the mid-forties to mid-fifties.
- Strong age-group and sub-elite endurance athletes reach the high fifties and sixties.
- Elite endurance athletes measure in the seventies, and the very highest recorded values go beyond eighty.
Two caveats that matter more than the ranges. First, values are typically lower in women than in men at the same training standard, for reasons of body composition and oxygen-carrying capacity rather than effort — which is exactly why Garmin's age-and-sex comparison is the number to read. Second, VO2 max declines with age in almost everyone, so a figure that would be unremarkable at 25 can be excellent at 55.
Why it barely moves once you are trained
This is the part that frustrates people most, and it is not a flaw in the watch.
VO2 max responds quickly to training when you start from a low base — the first months of consistent aerobic work produce real, measurable gains. Then it flattens. In a well-trained endurance athlete it is close to a plateau, and further improvement in performance comes from somewhere else entirely:
- A higher lactate threshold — the fraction of that ceiling you can hold for an hour.
- Better running economy — less oxygen needed for the same pace.
- Greater durability — holding those qualities together late in a long race.
None of those are VO2 max. Which means that for a trained runner, VO2 max is one of the worst available progress trackers: you can take two minutes off your 10K time over a season while the watch shows the same figure throughout. That is not the estimate failing. That is the estimate correctly reporting a quantity that did not change.
There is a reporting effect on top of this. Garmin shows a whole number, so a genuine one or two percent improvement can simply not appear. And the algorithm smooths across runs rather than reacting to one, so even real change arrives late.
Fitness age is the same number in a friendlier hat
Fitness age takes your VO2 max estimate, compares it with population norms for your age and sex, and reports the result as an age instead of a number. On current models it may also take in your resting heart rate, your activity level and your body composition, but the aerobic estimate is doing most of the work.
So the honest translation is: if your fitness age improves, your VO2 max estimate improved. It is a presentational layer, not independent evidence, and it inherits every error described above. A max heart rate set too low gives you an older fitness age for exactly the same arithmetic reason that it gives you a lower VO2 max.
That is not useless — restating a physiological estimate as an age is genuinely motivating for people who do not care about millilitres per kilogram per minute. Just do not treat it as a second opinion. It is the same opinion, rephrased.
The number worth training against instead
Here is the case for putting VO2 max down and picking up something else.
VO2 max is a ceiling: the maximum rate at which you can use oxygen. Racing is not done at that ceiling. Almost every endurance event longer than a few minutes is run at some sustainable fraction of it, and among athletes of similar standard, differences in race performance track that sustainable fraction far more closely than they track the ceiling itself. Two runners with identical VO2 max values can finish a half marathon minutes apart.
The fraction has a name. Your lactate threshold is the intensity at which lactate starts accumulating in your blood faster than you can clear it — below it you are in a steady state, above it a clock starts. It has three properties VO2 max does not:
- It can be measured directly rather than inferred, from a pinprick of blood at increasing intensities in a lab test.
- It moves with training on a timescale of weeks, so it actually works as a progress tracker.
- It converts into a pace and a heart rate you can use on Tuesday, which a ceiling figure does not.
Your watch does try to estimate it — though Garmin's automatic detection is fussy and fails silently, which is a problem in its own right. But once you have a threshold figure you trust, you can set your heart rate zones against it instead of against a percentage of an estimated maximum, and most of the arithmetic in this article stops mattering to you. That is the case for threshold over VO2 max, and it is not a marketing position — it is why coaches have worked this way for decades.
If you want the numbers turned into actual sessions, Lactate Training syncs your Garmin activities and health data and builds and adapts a plan with zones anchored to your lactate threshold rather than to 220 minus your age. And if you want to understand the rest of what your watch is telling you, every Garmin metric, grouped by what it is actually for.
Frequently asked questions
Is Garmin's VO2 max accurate?
It is a reasonable estimate of your own trend and a loose estimate of your absolute value. It is calculated from your pace against your heart rate relative to your maximum heart rate, so its accuracy depends entirely on that maximum being correct and on clean heart rate data. It is not a measurement, and it is not useful for comparing yourself with other people.
Why is my Garmin VO2 max going down?
The most common cause is a max heart rate set too low, which makes every effort look harder than it was and systematically depresses the estimate. Other frequent causes are bad heart rate data from an optical sensor, hot or humid weather, and a switch to hilly or trail running where GPS pace no longer reflects effort. Check your max heart rate before you change your training.
What is a good Garmin VO2 max?
Read it against your own age and sex rather than as an absolute. Committed recreational runners commonly sit in the mid-forties to mid-fifties, and elite endurance athletes in the seventies, but a value that is unremarkable at 25 can be excellent at 55. Garmin shows a fitness level band alongside the figure, and that comparison is more informative than the number.
Why won't my Garmin VO2 max increase?
Usually because you are trained enough that it genuinely is not increasing. VO2 max improves fast from a low base and then plateaus, while performance keeps improving through threshold, economy and durability. Garmin also reports whole numbers and smooths across runs, so small real gains may never appear. Track your threshold pace instead.
Is Garmin fitness age accurate?
It is about as accurate as the VO2 max estimate it is built from, because on current models that estimate does most of the work. It is a restatement rather than a second opinion, so any error in your max heart rate setting shows up in both. Useful as motivation, not as evidence.
Why does my VO2 max drop on trail runs?
Because the model compares your GPS pace with your heart rate, and climbing makes you slow at a high heart rate. There is no way for a pace-based estimate to pay you for vertical metres, so hilly and technical running looks like poor fitness. Judge the estimate from flat road runs.
Train the threshold, not the estimate
VO2 max is an inference about your ceiling. Your lactate threshold is the number your sessions should actually be built on. Lactate Training syncs your Garmin activities and health data and builds and adapts a plan with zones anchored to that threshold.