Run315

Sunday 15 Mar 2026, 07:30

running · read as steady

Run

16.95 km
1:22:35 moving
4:52 /km average
151 avg bpm · max 160
102 training load

7 C, 72% humidity, 1 C dew point -- good conditions, no correction worth making.

Running form

Over the running portion only

181spm
Cadence
±0 spread
1.13m
Stride length
240ms
Ground contact
7.5%
Vertical ratio
Bounce as a share of stride.

Second half against the first: cadence +0 spm, ground contact +0 ms. Pace went 5:02 /km to 4:56 /km, which moves cadence on its own.

Why you stopped

6:34 not running

Mostly held together, with 1 fatigue break late on.

2 Crossings 1 Rest stops 1 Fatigue
AtWhat it wasFor HRPace after
1.20 km Crossing
Short full stop with heart rate barely moving: a road crossing.
0:16 −4 -0.1% 75% sure
7.65 km Rest
Stood still long enough for heart rate to come down: a real break.
2:24 −35 +0.1% 80% sure
10.57 km Crossing
Short full stop with heart rate barely moving: a road crossing.
0:12 −2 +0.0% 75% sure
13.50 km Exhaustion
Late, heart rate still high while barely moving, and you never got the pace back: this was fatigue.
3:42 −0 +9.0% 85% sure

“Pace after” compares the 250 m before the interruption with the 250 m after. A stop you recover from costs nothing; fatigue shows up here.

Where you ran

275 points

Kilometre splits

Uneven — a workout, or a run that got away from you.

1 5:00 /km
2 5:24 /km
3 5:00 /km
4 5:00 /km
5 5:00 /km
6 5:00 /km
7 5:00 /km
8 7:32 /km
9 5:00 /km
10 5:00 /km
11 5:20 /km
12 5:00 /km
13 4:51 /km
14 6:57 /km
15 4:55 /km
16 4:55 /km
17 4:55 /km

Longer bar is faster. Last split may be partial.

Best efforts in this run

DistanceTimePacevs record
0.40 km 1:48 4:31 /km +0:21
0.80 km 3:37 4:32 /km +0:43
1.00 km 4:37 4:37 /km +0:52
1.61 km 7:40 4:46 /km +1:25
3.00 km 14:46 4:55 /km +3:08
5.00 km 24:57 4:59 /km +5:33
10.00 km 52:29 5:15 /km +11:10
15.00 km 1:19:27 5:18 /km +9:11
16.09 km 1:25:19 5:18 /km +9:42

Signals

+4.5%
Cardiac drift
Some drift — warm conditions, or the top end of easy.
50
Metres climbed
908
Calories
, so the check has to wait for the parsed document. addEventListener('DOMContentLoaded', function () { try { var dm = ['standalone', 'minimal-ui', 'fullscreen', 'window-controls-overlay']; if (!document.getElementById('frozen-note') && (navigator.standalone || dm.some(function (m) { return matchMedia('(display-mode: ' + m + ')').matches; }))) { var pk = 'portal-installed', reg = JSON.parse(localStorage.getItem(pk) || '{}'); reg.Run315 = Date.now(); localStorage.setItem(pk, JSON.stringify(reg)); } } catch (e) { /* private mode - ignore */ } }); // Installable, and readable on the train. See templates/sw.js. if ('serviceWorker' in navigator) { addEventListener('load', function () { navigator.serviceWorker.register('/Run315/sw.js'); }); }
Static demo. A synthetic athlete, frozen to files — every page here is the real app rendering real analysis, but anything that writes (Garmin sync, adding a race, the coach review) is switched off, because a file server has nothing to write to. Source & how to run it for real.