--- date: 2026-09-23 type: run tags: [run, afternoon, sprint, max-hr-test, under-read] --- # Run — 2026-09-23 (max-HR sprint test) **1.39 km in 15:13 — mostly a walk/jog at 10'57" avg, plus an all-out ~100 m sprint (burst 2'34") to find max HR. The watch read 165 bpm max — almost certainly an under-read: he nearly threw up, and the sensor cadence-locked (cadence maxed at 241 spm).** ## Data | Metric | Value | |--------|-------| | Distance | 1.39 km | | Duration | 15:13 | | Avg pace | 10'57" /km (walk/jog warmup) | | Fastest pace | 2'34" /km (the sprint burst) | | Avg HR | 128 bpm | | Max HR | **165 bpm (under-read — see verdict)** | | Cadence | 115 spm (max 241 — sensor locked to arm swing) | | Stride | 79 cm · 1,764 steps | | Metric | Value | |--------|-------| | VO₂Max | 46 ml/kg/min | | Recovery time | 8 h | | Total / active calories | 139 / 116 kcal | **HR zones:** Extreme 0 · Anaerobic 1 min · Aerobic 3 min · Fat-burning 7 min · Warm-up 1 min. ## Sleep — Night before **8h 20min** · 00:26→09:00 · REM: 11% · Deep: 30% · HRV: 126 · Resting HR: 49 · Score: 87/100 > See [[Sleep/2026-09-23]]. ## How it felt > "Tried to measure my max HR with an all-out sprint but it did not measure well. HR only went up to ~165, which is not real — I could not stand still and almost threw up after the ~100 m sprint." ## Verdict **The 165 is not your max HR — and the watch itself is the proof.** Three things stacked up to under-read it: 1. **The sprint is too short for the *heart* to peak.** Heart rate physically lags effort by ~20–30 seconds. A 100 m sprint is ~15 seconds — it's over before your HR even begins to climb toward its true ceiling. Even a perfect sensor would read the *recovery* peak, not the sprint peak. 2. **The optical sensor lagged and smoothed it.** Wrist HR (light-based) averages over a ~10–20s window. A 15-second spike gets flattened out, so the "165" is closer to "where HR was ~30s after you stopped" than "where it was mid-sprint." 3. **The smoking gun: cadence maxed at 241 spm.** During a max sprint the arm swing is violent, and the wrist sensor "cadence-locks" — it mistakes your arm cadence for your pulse and reads the wrong signal. A 241 spm cadence reading next to a 165 bpm "max" is the sensor telling you it lost the pulse and grabbed the motion instead. You're 23 and you just nearly vomited from a 100 m effort — your true max is almost certainly **in the 185–200 range**, not 165. **How to actually measure it (for real):** 1. **Warm up properly** — 15–20 min easy, so the heart is already responsive before the test. 2. **Make the peak effort long enough to register** — a single 15s sprint can never do it. The standard field test: after the warmup, do **3 hard uphill repeats of ~2–3 min** (or 400–600 m all-out) with ~1–2 min recovery, finishing with one final **30–60s all-out** burst. The highest number in that last minute is your max. 3. **A chest strap is the real answer.** For max-HR and sprint work, the wrist optical sensor fundamentally can't track fast changes — a chest strap (ECG) will catch the actual peak. If max HR matters to you (it sets your training zones), it's worth borrowing/grabbing one for the test. **But — don't over-index on this right now.** For setting training zones, your watch's *current* estimates (and especially your lactate-threshold HR, which the watch tracks better than raw max) are more useful than a one-off max. The useful numbers from today are already in the log: 143 bpm avg at 7'03"/km on the 2 km leg, VO₂Max stable at 46. You don't need a perfect max-HR number to keep training well this month. ## Connected - [[Sleep/2026-09-23]] (the night before) - [[Runs/2026-09-23]] (the 2.01 km warmup leg ~30 min earlier) - [[Half-marathon-plan]] (the block this max-HR test was meant to calibrate)