Files

62 lines
3.5 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
date: 2026-10-02
type: run
tags: [run, afternoon, 5k-pb, hard-effort, off-plan-effort]
---
# Run — 2026-10-02
**5.33 km in 33:39 — 6'19" avg at 159 bpm (max 179). First dedicated 5k, 31:42 — a 5k PB by ~7 minutes over anything before it — with a 5'33" fastest km (km 4). But it landed on the Friday "actually easy" slot, on a 112ms / 6h23 night, with lunch still sitting in his stomach. The PB is real; the timing is the same over-effort trap as Sep 30.**
## Data
| Metric | Value |
|--------|-------|
| Distance | 5.33 km |
| Duration | 33:39 |
| Avg pace | 6'19" /km |
| Fastest pace | 5'33" /km (km 4) · burst 4'30" |
| Avg HR | 159 bpm |
| Max HR | 179 bpm |
| Cadence | 160 spm (max 184) |
| Stride | 99 cm · 5,402 steps |
| Metric | Value |
|--------|-------|
| 5k split | **31:42 (PB)** |
| HR recovery (2min) | 24 bpm (dropped 24, 171→123) |
| VO₂Max | 46 ml/kg/min (held, "average") |
**HR zones:** Extreme 1 min · Anaerobic 18 min · Aerobic 9 min · Fat-burning 2 min · Warm-up <1 min. **Splits:** 6'48" → 6'14" → 5'41" → 5'33" → 7'26" + 0.33 km in 1'57".
## Sleep — Night before
**6h 23min** · 01:35→08:00 · REM: 18% · Deep: 25% · HRV: **112** · Resting HR: 52 · Score: 82/100
> Late bed + phone in bed + hard onset — the shortest, lowest-HRV night of the recent log. See [[Sleep/2026-10-02]].
## How it felt
> "Falling asleep was hard, insomnia a bit, too much phone in bed lately. Run was a bit harsh, didn't digest lunch fully, but it was a PB!!"
## Verdict
**The PB is real — celebrate it, then let Sunday be the work.** 5.33 km with a 31:42 5k split is his first proper 5k and a genuine personal best: the fastest he'd covered 5k before was ~39–40 min, and only inside the long runs with shoe-stops. Fastest km 5'33", a 4'30" burst, VO₂Max pinned at 46 again, and HR recovery strong at 24 bpm (171→123). The engine and the speed are both there, and doing it on a 112ms / 6h23 night is a quiet credit to the fitness — a suboptimal night didn't stop the PB.
But the timing says this was the wrong day to prove it, and it's the *same* wrong day as two weeks ago:
1. **Friday is the "actually easy" slot — 48h before Sunday's long run.** The Sep 30 note said it in so many words ("HR 135–150, first km 7'30"+"), and instead he ran 5.33 km at 159 avg with 19 of 33 min in extreme + anaerobic. Sep 25 also ran hot on a Friday. The block grows on Sunday's long run, not on these — a hot Friday is load Sunday has to absorb on top of everything else.
2. **The night before was the weakest in weeks** (112ms, 6h23, bed 01:35). PB'ing on top of that means the effort taxed a system already behind on recovery.
3. **"Didn't digest lunch fully"** — an afternoon run on an unsettled stomach, so part of the "harsh" feel is GI, not fitness. Not a reason to chase PBs on a full stomach.
The splits tell the 5k-race story cleanly: patient first km (6'48"), then a surge to 5'33" on km 4, paid for with a 7'26" km 5, then a 1'57" kick over the last 0.33 km. He went for it, died a bit, and kicked. That's a race, not a training run — and that's exactly what a Friday easy day shouldn't be.
Net: bank it, own it, then keep Sunday honest. The 5k PB is a milestone; the half-marathon is the project. Don't let "PB" become the new "easy."
## Connected
- [[Sleep/2026-10-02]] (the 112ms / 6h23 night this PB came on)
- [[Runs/2026-09-30]] (the Friday-easy warning this ignored — same trap)
- [[Runs/2026-09-27]] (the 13.06 km distance PR — the block's real project)
- [[Half-marathon-plan]] (Sunday long run is the one that grows)