Garmin VO2max: How Far Off Is Yours? (94 Paired Powertests, 2026)

Your Garmin says 52. Is it right? In 94 cases where we could hold Garmin's own VO2max number against a measured Powertest, the watch read two points high on average — and how far off it lands depends on how fit you already are.

What Garmin Actually Measures

Modern Garmin watches do not measure VO2max in the lab-physiology sense. They estimate it from the relationship between heart rate and pace (or power on a cycling computer) during your everyday rides and runs. The algorithm — most commonly the FirstBeat HRV-and-load model — looks for sub-maximal data points and projects forward to what your maximum oxygen uptake would be if you pushed all the way to exhaustion.

It is a remarkably good engineering trick for a free, always-on estimator. But "estimator" is the right word, and an estimator carries a bias. The question for any athlete reading a number on the wrist is: how big is the bias in my fitness range, and which direction does it pull?

How We Tested It

A Mader-model Powertest measures both VO2max and VLamax directly from a short maximal protocol. It is a field test on your own bike — no mask, no treadmill, no appointment — and it is the reference every figure in this article is measured against. We have run 10,706 valid Powertests, 9,297 of them on the bike, and a subset of those athletes also wear a Garmin watch that reports a VO2max estimate of its own.

For this analysis we paired 94 observations: a bike Powertest against the VO2max number Garmin itself reports for that athlete, dated close enough that no meaningful fitness change happened in between. That is the source, stated plainly — Garmin's number, not our model's estimate of it.

We are not claiming "15,000 watch comparisons". We are claiming 94. Where a fitness bucket rests on only a handful of athletes, you will find the count in the table rather than buried in an average.

The Headline Numbers

Two numbers carry this article. The first is the bias: on average Garmin reads two points high, and the correlation of 0.883 says it does track real fitness — this is a good estimator, not a random number generator.

The second number is the one that actually matters. The slope is 0.751, not 1.0. A watch that followed the measurement one for one would sit at 1. At 0.751 every value gets pulled toward the middle: low readings come out too high, high readings too low. The two lines cross at 67.9. Below that, Garmin flatters you. Above it, Garmin sells you short.

The Bias Curve — And Why It Flips

The most useful view of this data is the bias broken out by fitness bucket. It shrinks from bottom to top, and at the elite end it crosses zero.

Read the n column first. The untrained bucket rests on seven athletes. That is an order of magnitude, not a precise figure — take it as "roughly eight to nine points too high" and nothing sharper. The other three buckets carry 28 to 30 athletes each, and those you can lean on.

Now read from top to bottom. An untrained rider whose measured VO2max is 41 sees about 50 on the wrist. A recreational rider at 51 sees 54. A trained rider at 60 sees 62. And an athlete at 72 sees 71.6 — that is a direct hit, half a point apart.

So the headline is not that Garmin goes soft on elite athletes. It is the reverse: Garmin is accurate at the top and generous at the bottom. The fitter you get, the more honest your watch becomes.

Why Regression Toward the Mean Explains This

This is the textbook signature of an estimator anchored on a population prior — and in this data it is no longer a hypothesis. It is measured. The best-fit line has a slope of 0.751: one point of real, measured VO2max shows up as three quarters of a point on your wrist. The algorithm carries a built-in expectation of what a normal VO2max looks like, and whenever your submaximal heart-rate-to-power data leaves room for interpretation, it pulls your value toward that expectation.

That compression is exactly why the crossing point matters. At a true VO2max of about 68, the watch is right — not by luck, but by construction. Below it you get flattered, above it you get short-changed, and the further you sit from 68 in either direction, the wider the gap.

How to Interpret Your Garmin Number

Here is a one-step correction you can apply with no math:

This is not a substitute for a measurement, it is a sanity check. The corrections are central tendencies for our cohort, and the individual scatter around them is large: the standard deviation of the bias across all 94 pairs is 5.06 points, the mean absolute error 4.12. Read the table as "your true value is probably in this region", never as "your true value is exactly this".

Once you have landed on a likely true number, see where it ranks for your age and sex on the VO2max chart by age — that context tells you whether to keep chasing or hold what you have built.

What About Apple Watch and Polar?

We do not yet have a paired comparison cohort for non-Garmin watches at the same level of methodological rigour. From the published literature and the broader VO2max-watch comparison work that does exist:

Apple Watch uses a similar HR-and-pace inference (built on the Sports Science team's own model rather than FirstBeat). Independent studies report mean biases in the same ballpark — roughly +2 to +5 points for running, somewhat noisier for cycling without paired power data. The directional bias toward over-estimation appears to hold.

Polar is the most honest of the three about uncertainty: the watch returns a VO2max value with a stated confidence band, and Polar's documentation explicitly notes that the estimate degrades for fitness levels far from the population centre. Published comparisons report bias magnitudes similar to Apple's, with slightly tighter dispersion.

The honest summary: across all three brands, the direction of the bias (over-read for the untrained, accurate near the trained mean, under-read at the elite end) appears to be a property of HR-based VO2max estimation in general, not a specific brand failing.

The Measurement That Doesn't Need a Correction

Everything above is a workaround for one root problem: your watch estimates a single number at the wrist, and that estimate carries a bias you have to undo by hand. There is a way to skip the correction entirely — measure instead of guess.

Here is the part most people miss: the rides you already upload to Garmin hold the data to do it. Connect your Garmin to A Faster You and we read those existing sessions to place your real VO2max — the two-engine version, VO2max and the VLamax the watch cannot see at all — then build a plan that adapts to each session to raise it. No lab, no bias-curve lookup, and a coach that tells you why your numbers move, not just that they did.

Connect your Garmin and see your real number →

Want the measured version instead of an estimate? The Mader-model Powertest takes 25 minutes on your own bike and pins your VO2max and VLamax exactly — it is the reference behind every figure in this article. Most A Faster You athletes run their first in week one, then re-test every 4–6 weeks: run a Powertest →

Once you have landed on a real number, see where it ranks for your age and sex — and what race times it predicts — in our VO2max chart by age →. For what "trained" looks like across distances and rider types, our larger cohort report compares 3,491 athletes to ACSM norms: VO2max & VLamax cohort report →

FAQ

Why does my Garmin VO2max change by 2 points day to day? The estimator updates after every aerobic activity, and the underlying HR-to-pace relationship is noisy: caffeine, sleep, ambient temperature, and hydration all shift it by a few percent. Trust the 28-day trend, not any single day. The day-to-day jitter is normal and is not a sign that your fitness genuinely fluctuated.

Is the watch number reliable as a trend, even if the absolute value is off? Mostly yes. The bias direction tends to be consistent for a given athlete over months, so a watch-reported increase from 50 to 53 generally reflects a real fitness gain, even if your true VO2max is closer to 48 throughout. Treat the trajectory as a signal; treat the absolute number as a rough anchor.

Does running vs. cycling matter for the watch number? Far less than most people assume. We checked the 240 athletes for whom Garmin reports both a running and a cycling VO2max: in 94.6% of them the two numbers are identical. The watch is not running two separate models — for almost everybody it publishes one number under two labels. So if you were hoping the running figure would settle the argument, it is usually the same figure.

My Garmin says 60 but my Powertest came back 50. Which should I believe? Believe the Powertest. It is a measurement; the watch number is an inference from heart rate. A 10-point gap is on the higher end of what we see, but it is in line with what the bias curve predicts for a recreational rider whose Garmin sits near the population mean.

Will my Garmin number get more accurate if I do more rides? Slightly, yes — the algorithm benefits from more sub-maximal data points and from heart-rate samples close to threshold. But it will not converge on your true value; the bias is structural, not data-volume-limited.

Does training to push my VO2max up actually move the watch number? Yes, in the same direction, but compressed. With a slope of 0.751, three real points (Powertest +3) show up as a little over two watch points. Plan from the Powertest delta, not the watch delta.

Are the watch VO2max numbers safe to share with a coach? For broad context, yes. For prescribing training zones, no — wrist-based VO2max is too noisy to anchor zone calculations. A coach who plans from a watch number is planning from an estimate of an estimate.

Sources: Mader, A. (2003) — Glycolysis and oxidative phosphorylation as a function of cytosolic phosphorylation state and power output of the muscle cell. Eur J Appl Physiol, 88(4–5), 317–338. Mader, A. & Heck, H. (1986) — A theory of the metabolic origin of the "anaerobic threshold". Int J Sports Med, 7 Suppl 1, 45–65. Bassett, D.R. & Howley, E.T. (2000) — Limiting factors for maximum oxygen uptake. Med Sci Sports Exerc, 32(1), 70–84. FirstBeat Technologies — Automated Fitness Level (VO2max) Estimation with Heart Rate and Speed Data (white paper, 2014, updated 2019). Cohort: 10,706 valid Powertests (9,297 of them on the bike) with 94 bike-paired Garmin-reported VO2max observations, A Faster You internal database, snapshot 2026-08-12.