Files

3.9 KiB
Raw Permalink Blame History

date, type, tags
date type tags
2026-09-25 run
run
midday
hard-effort
negative-split
post-alcohol

Run — 2026-09-25

4.01 km in 23:56 — 5'58" avg at 163 bpm (max 180). A hard, negative-split midday effort (6'03" → 5'35") the day after 1.2 L of beer, with no sleep data to cross-reference. VO₂Max held at 46, but 16 of 24 min sat in anaerobic/extreme — the wrong run for a Friday.

Data

Metric Value
Distance 4.01 km
Duration 23:56
Avg pace 5'58" /km
Fastest pace 5'35" /km (km 4) · burst 4'38"
Avg HR 163 bpm
Max HR 180 bpm
Cadence 164 spm (max 182)
Stride 102 cm · 3,926 steps
Metric Value
HR recovery (2min) 22 bpm (dropped 22, 179→135)
VO₂Max 46 ml/kg/min (held, "average")
Recovery time 24 h
Total / active calories 337 / 301 kcal

HR zones: Extreme 4 min · Anaerobic 12 min · Aerobic 4 min · Fat-burning 1 min · Warm-up <1 min. Splits: 6'03" → 6'27" → 5'48" → 5'35" + 0.01 km in 0'03". Running form: ground contact 291 ms (Good), balance L 49.9 / R 50.1 (clean).

Sleep — Night before

No watch sleep data recorded. Gutca reported 1.2 L of beer the night before — no HRV or sleep metrics to cross-reference.

How it felt

"A bit challenging — the speed run from Wednesday is still in my legs, in the back of my thighs. But breathing felt better, not as hard as it used to be: every 2 steps in through the nose, 2 steps out through the mouth. The rhythm collapsed a few times but I got it back. Felt okay, I guess."

Verdict

The engine is fine; the day was wrong. 5'58" avg is the fastest sustained pace in the recent log — faster than the 10 km PR's ~6'30" running pace — and the negative split (6'03" → 5'35", finishing fastest) says pacing and legs held. VO₂Max pinned at 46, balance clean. Nothing broke.

Two things worth separating. The "challenging" feel is real but local — the back-of-thigh soreness is DOMS from Wednesday's sprint test (a 100 m all-out is a hamstring workout), and a threshold 4 km on sore hamstrings is exactly what "hard but manageable" feels like. And the breathing is a quiet win: at 163 bpm he held a 2-step-nose / 2-step-mouth rhythm and pulled it back when it broke — a month ago that HR would have been mouth-breathing chaos. The aerobic floor is rising even though today's effort sat too high.

But this was a threshold effort, not an easy Friday. Avg HR 163 sits right at the anaerobic boundary (easy is 135–150), and 16 of ~24 min landed in anaerobic + extreme. Friday is the "short and boring" run 48 h before Sunday's long run — this was neither. The load it banked is load the long run has to absorb.

The beer is part of the number, not all of it. 1.2 L yesterday means dehydration and a depressed HRV, and HR runs ~5–10 bpm hot at any given pace on top of that. So a chunk of that 163 is alcohol tax, not effort — but the pace itself (5'58") is genuinely hard either way, so this wasn't a drunk-easy-run masquerading as work. With no sleep data there's no way to see the HRV hit, but a drinking night feeding a hard run is the exact "decay, not rest" pattern — real rest shows as 110–135 ms nights, and this one has no signature at all.

HR recovery 22 bpm (179→135) is okay, but the 135 endpoint is high — HR stayed elevated, and the watch asks for 24 h. That's the bill landing on Sunday.

Sunday is the one that matters now. Run the long run easy — HR 135–150, conversational, walking allowed, time on feet over pace. Don't let today's push bleed into it. Today was a decent hard run on a day that didn't ask for one; the block grows on Sunday, not here.

Connected