Your Zone 2 Ceiling Is Wrong — Here's How to Fix It¶
Your watch told you zone 2 accounted for 68% of last Thursday's easy run. That number came from a formula — 220 minus your age — that has never been validated in a lab. A peer-reviewed paper published in 2025 puts a specific number on the error: depending on which submaximal threshold marker anchors the zone, the coefficient of variation across individual runners ranges from 6 to 29%. At a practical level, that means two runners with identical max heart rates can have a zone 2 ceiling that differs by 15 to 20 bpm.
You have been training to a number that is probably off. The question is how far off, and how to fix it.
The Number Your Watch Is Computing (And Where It Came From)¶
The 220-minus-age formula traces back to a 1971 review by Fox, Naughton, and Haskell. It was not a controlled trial. It was not derived from a large sample of athletes. It was a line fit to a compilation of published data that the authors themselves described as a rough approximation. It became a standard because it was simple, not because it was accurate.
The American College of Sports Medicine has published the standard deviation on the formula's predictions for decades: ±10–12 bpm. That means your predicted max heart rate could plausibly fall anywhere in a 20–24 bpm range centered on the formula's output — and that is just the error in predicting maximum heart rate. Zone 2 is not computed from your max HR in isolation. It is set as a percentage of that estimate, which compounds the error at the zone boundary.
Every major platform defaults to this formula unless you override it manually. Garmin uses it. Apple Watch uses it. Polar uses it. Strava uses it. Unless you have gone into the settings and entered a custom number based on a real test, your watch is basing every zone calculation on a population average with a ±12 bpm standard deviation applied to a number that is already an estimate.
The formula is not wrong the way a typo is wrong. It is wrong the way a national average is wrong when applied to one person.
What the 2025 Research Actually Found¶
A 2025 paper in PMC11986187 — "Zone 2 Intensity: A Critical Comparison of Individual Variability in Different Submaximal Exercise Intensity Boundaries" — compared the zone 2 boundary across six different threshold-based definitions in the same group of runners. The finding was not that the formulas disagreed slightly. It was that the coefficients of variation ranged from 6% to 29% depending on which physiological marker anchored the upper limit.
A CV of 29% on a heart rate that averages around 150 bpm translates to a standard deviation of roughly 43 bpm. Even the lowest-variability definition in the paper produced a CV of 6% — still a standard deviation of 9 bpm around the zone boundary. The implication is not that the zone is slightly imprecise. It is that two runners who look identical on paper — same age, same max HR — can have a physiologically correct zone 2 ceiling that differs by 15 to 20 bpm.
To make that concrete:
| Runner A | Runner B | |
|---|---|---|
| Age | 38 | 38 |
| Max HR | 185 bpm | 185 bpm |
| Formula-derived zone 2 ceiling | 148 bpm | 148 bpm |
| Physiologically calibrated ceiling | 140 bpm | 158 bpm |
| Difference from formula | −8 bpm | +10 bpm |
Runner A is running aerobic intervals inside zone 2 every time the watch logs it as easy — but their actual aerobic threshold is 8 bpm lower. They are spending "easy day" minutes slightly above their true zone 2 ceiling, accumulating more stress than the data shows. Runner B's real ceiling is 10 bpm higher than the formula assumes, meaning runs labeled zone 2 to 3 crossover are genuinely easy for them — and they may be undertraining on days they thought were appropriate.
Separately, the expert consensus published in IJSPP Vol. 20, Issue 11 (2025) — a panel of exercise physiologists asked to agree on a universal zone 2 definition — could not reach one. The authors were explicit: individual variability in the relationship between physiological thresholds and heart rate makes a fixed universal boundary scientifically indefensible. Running media picked this up in early 2026, but the practical calibration question has not been answered for self-coached runners.
This post answers it.
Why This Breaks Every HR Metric in Your Strava and NavRun Reports¶
Your zone distribution charts do not produce zone assignments. They inherit them. Whatever ceiling your watch or Strava has stored for zone 2 becomes the boundary that every downstream tool — including NavRun — uses to classify every beat of every run.
The specific outputs that go wrong when that ceiling is off:
- "Time in Zone 2" (Strava weekly summary) reads as a percentage of a zone that was defined by the wrong boundary. If your real ceiling is 8 bpm lower than what Strava has, time you recorded inside "zone 2" includes minutes your physiology experienced as zone 3 effort. The percentage is not just approximate — it is categorically misclassified.
- "Easy day" confirmation in NavRun's weekly report may flag a zone 2 run as moderate or hard if your real aerobic threshold sits meaningfully below the formula's estimate. The weekly training report numbers are only as trustworthy as the zone boundaries they are benchmarked against.
- Training load calculations that weight zone time assume the zones are accurately assigned. A week that looks like 70% easy / 20% moderate / 10% hard on the chart may be 55% easy / 35% moderate / 10% hard in physiological terms.
This is not an argument that the reporting tools are broken. It is an argument that the input they were given — your zone ceiling — is wrong, and correcting it takes one field test and one settings update.
For the broader case that Strava data needs context to be useful, Your Strava Data Is Missing the Big Picture covers that. This post is about the one specific input that makes heart rate data meaningful: whether the zone boundaries are yours.
The 20-Minute Field Test That Replaces the Formula¶
The gold standard is a lab lactate test — a measured LT1 from blood draws at increasing intensities. Accurate to within 1–2 bpm. Also: not available at 6 a.m. before a weekday run.
The field test below correlates within approximately 5 bpm of a lab LT1 for most trained runners. That is sufficient precision to materially improve on a formula with a ±12 bpm standard deviation. You need a heart rate monitor, 30–35 minutes, and a flat surface.
-
Warm up for 10–12 minutes at genuinely comfortable pace. Conversational. You could answer a question in three sentences without catching your breath. Do not skip this — arriving at the test segment while still warming up produces an artificially elevated reading.
-
Increase pace to where you can speak a full sentence but would not want to string together two. This is the approximate aerobic threshold — the first ventilatory threshold (VT1), the physiological marker that best defines the zone 2 upper limit in the PMC11986187 analysis. If you have to pause mid-sentence to breathe, you are above it. If you can deliver a paragraph without effort, you are below it.
-
Hold that pace for 20 minutes without adjusting. If the pace drifts the talk test back to fully comfortable, add a small increment. If you start losing the ability to speak a sentence, back off. Small corrections only — the goal is to find the pace and hold it.
-
Record average heart rate over the final 10 minutes only. Discard the first 10 minutes of the effort — HR takes time to stabilize at a given intensity, and the opening minutes capture drift rather than steady state. Most GPS watches allow you to see a lap average for a manually triggered lap; start the lap at the 10-minute mark if yours supports it.
-
That average is your zone 2 ceiling. This is your aerobic threshold heart rate — the highest HR you can sustain in a true aerobic state without beginning to accumulate lactate meaningfully. Some runners will find this aligns closely with what their watch already had. Others will find a 10–15 bpm discrepancy. Both outcomes are useful information.
-
Subtract 5–10 bpm to define your zone 2 floor. If your ceiling came out at 148 bpm, your zone 2 sits between roughly 138–148 bpm. The floor is less critical than the ceiling for daily training decisions — the boundary that matters most is whether you are crossing the upper limit, not whether you are high or low within the zone.
A few notes: temperature and humidity shift your heart rate at a given effort. Run the test in conditions that reflect your normal training environment. If you run most of your easy runs in 75°F and humidity, do not run the field test on a 50°F morning — the result will be slightly pessimistic. And re-run the test, not just rely on one reading: if two tests within a week give you results within 3 bpm of each other, you have a reliable number.
How to Enter Your Real Zone 2 Into Your Watch and Strava¶
You have a number. Now put it in the right place.
Garmin: Settings → User Profile → Heart Rate → Heart Rate Zones → set to Custom. Enter your zone 2 upper limit as an absolute bpm value, not as a percentage of HRmax. Garmin defaults to percentage-based zones, which re-introduces the formula error through the back door. Custom absolute values are the only setting that locks in your calibrated number.
Apple Watch (via iPhone Health app): Health → Browse → Heart → Heart Rate Zones → Customize Zones. Apple Watch allows per-zone absolute bpm entry. Set zone 2 upper limit to your field test result.
Strava: Settings → My Profile → Heart Rate Zones → enter your custom boundaries directly. Strava's effort calculations — including the "Relative Effort" score that appears on every activity — use these zone assignments. Updating them here changes what feeds NavRun if Strava is your HR data source.
NavRun: NavRun ingests HR data from your connected Strava account. Once Strava zones are updated, the zone distribution in your NavRun weekly reports will reflect the corrected boundaries on all future activities. Activities recorded before the update will retain the old classification — there is no retroactive reprocessing.
How Often to Re-Calibrate¶
Your aerobic threshold is not a fixed number. As fitness improves, LT1 typically rises — the runner becomes more aerobically efficient, sustaining higher intensities without crossing the threshold. A ceiling that was accurate in week one of a training block may be 3–5 bpm low by week twelve. That is a feature, not a problem: it means the training is working. But it also means the zones you calibrated in January do not necessarily reflect your physiology in April.
The practical rule: re-test at the start of each new training block, and after any significant break from structured training. Every 8–12 weeks during an active build is appropriate. Two or three calibrations per year is enough for most runners — you are not trying to chase a moving number weekly, just ensure it does not drift far enough to corrupt months of data.
One trigger worth flagging specifically: if you run the field test and find your new ceiling is 5+ bpm higher than what you measured three months ago, update your watch settings before the next training week. Do not let stale zones undercount the easy work you have actually earned.
Fix the Foundation, Then Trust the Data¶
Every HR-labeled metric in your weekly training report — time in zone, easy/moderate/hard distribution, zone-weighted training load — sits on top of one foundational input: where your zone 2 ceiling is set. If that number was produced by 220 minus your age, it has a ±12 bpm error band baked in, and the 2025 peer-reviewed research (PMC11986187) confirms the individual variability can push that spread to 15–20 bpm across athletes at the same max HR.
The field test takes 30 minutes and produces a number that is actually yours. The settings update takes five minutes. After that, the zone bars in your weekly report mean something.
If you have not already connected Strava to NavRun, do that first — the weekly report is where calibrated zone data pays off most clearly. Then run the field test, update your settings, and look at next week's report with a number you measured instead of a formula you inherited.
Not sure what to watch for in the weekly numbers once your zones are calibrated? Start here.
FAQ¶
Q: My watch shows max HR from an actual run — does that fix the formula problem?¶
Partially. If your watch recorded a true max HR during a race or all-out effort, using that number instead of 220-minus-age removes one layer of error. But zone 2 is set as a percentage of max HR — and the percentage used (typically 60–70%) is also population-derived, not individually calibrated. You can have an accurate max HR and still have a zone 2 ceiling that does not correspond to your actual aerobic threshold. The field test solves both layers simultaneously.
Q: How close does the talk test field test get to a lab lactate measurement?¶
Within approximately 5 bpm for most trained runners in controlled conditions. A 2021 systematic review in the Journal of Strength and Conditioning Research found the first ventilatory threshold (which the talk test approximates) correlates strongly with LT1 in endurance athletes. A 5 bpm uncertainty is materially better than the ±12 bpm standard deviation of the 220-minus-age formula.
Q: My Garmin only lets me set zones as percentages of max HR. What should I do?¶
Look for the "Custom" option under heart rate zone settings rather than one of the presets (Garmin, Polar, Joe Friel, etc.). In Custom mode, Garmin allows absolute bpm values. If your device firmware does not support absolute bpm zones, convert your ceiling to a percentage using your actual measured max HR — not the formula estimate — and enter that percentage. Either way, avoid letting the device back-calculate zones from 220-minus-age.
Q: Will recalibrating my zones affect my Garmin performance metrics like VO2max or Training Status?¶
Yes, but correctly. Garmin's FirstBeat-derived metrics (VO2max estimate, training load, anaerobic training effect) use the stored zone boundaries to classify effort. If your calibrated ceiling is 10 bpm higher than the formula assumed, sessions that Garmin previously counted as moderate will now correctly classify as easy. Your Training Status readout may shift — that shift reflects reality, not a downgrade in fitness.
Q: How do I know if the discrepancy between my formula-based zone and my field test result is typical?¶
The PMC11986187 paper found the spread across different threshold-based definitions reaches coefficients of variation up to 29%. A 10–15 bpm discrepancy from the formula is not unusual — it falls well within the documented individual variability. The runners who tend to see the largest discrepancies are those with a high aerobic efficiency relative to age (experienced runners whose threshold sits high relative to their max HR) and those with an atypically high or low actual max HR.