Race report: Helsinki Midnight Run 2026 — 10 km

On Friday evening… no, to be precise, Saturday evening on 12 Sep, it was time for the Helsinki Midnight Run 2026, a 10 km evening/night race through central Helsinki. The photo is from the start area on Senate Square shortly before the gun — the race didn’t start until 21:12, true to its name.

The goal

Week 37’s plan set the goal at comfortably beating an hour: 52–55 minutes, a steady pace of about 5:12–5:30 min/km for the whole distance. The anchor was Monday’s tempo segment (31.5 min at 5:54 min/km, heart rate 161–169) — based on that, threshold pace was close to the target pace.

The result

The official race time was 57:48 — the race organizer’s timed result, the most accurate figure available. The Watch’s own GPS data gives a slightly different number: the whole session’s length was 57.9 min / 10.13 km (average pace 5:43 min/km, average heart rate 167, max 180), and if you look at exactly when the GPS distance crossed the 10.00 km mark, the data says 57:16 — about 32 seconds faster than the official result. The gap is likely explained by small differences between GPS and the official course measurement (GPS cuts corners slightly shorter) plus start-line timing; the official time (57:48) is what’s used for comparing against the goal from here on.

57:48 is clearly under an hour — by about 2 minutes 12 seconds — but falls outside the targeted 5–8 minute margin.

Pacing: what the second-by-second data reveals

The whole race’s average pace (5:43 min/km) is again too coarse a picture of what actually happened. The data splits into three clear phases:

Phase	Duration	Distance	Pace	Avg HR	Max HR
Start	10.00 min	1,821 m	5:30 min/km	166	173
Mid-race dip	19.00 min	3,118 m	6:06 min/km	162	167
Finishing surge	29.00 min	5,187 m	5:35 min/km	171	177

So the race started fast — even faster than the target pace (5:30 min/km) — but around a third of the way in, pace clearly slowed for 19 minutes (6:06 min/km), while heart rate also dropped slightly (162 vs. 166 at the start). This isn’t a GPS glitch but a real dip: pace and heart rate fell together. What followed, though, was a strong finishing surge — over half the entire distance (5.19 km) at 5:35 min/km, heart rate climbing to 171–177, the highest of the whole race.

What this teaches

Two things stand out. First, the start was too hard relative to what could actually be sustained — 5:30 min/km for the first ten minutes inevitably led to a dip once the body couldn’t hold it. Second, and this is the more encouraging finding: the ability to find another gear mid-race and push over half the distance again at a harder pace (5:35 min/km, heart rate even above Monday’s tempo segment) shows the finish wasn’t limited by fitness but by pacing. A steadier start, say 5:45–5:50 min/km, would likely have allowed a more even effort across the whole distance and a result closer to the 55-minute target.

The goal (52–55 min) wasn’t fully met, but 57:48 is still a clear sub-60 result, and the finishing surge’s data gives a concrete, measurable lesson for the next race: a more restrained start, saving the reserve more evenly across the whole distance.

Follow the journey and training diary here at puhakka.org!