Numbers with context

Every pace calculator on the internet treats a run as a distance and a time. Every runner knows that is wrong. This release is about the rest of the picture.

The same pace is not the same run

Calcpace now takes temperature and altitude as inputs. Log a run with them, or feed them to the calculator, and the analysis adjusts: what you ran, and what that performance would have been worth in neutral conditions.

That gives you the comparison that was missing. A tempo effort at 30°C is not the effort the same pace represents on a cool morning, and 2,000 metres up it is a different run again. The August long run that felt like a disaster and the October one that felt easy can now be put side by side on equal terms — and quite often the summer run turns out to have been the better one.

The fields sit behind a toggle on the activity form rather than in your face. Most runs do not need them, and the ones that do, you will know about. There is a proper date picker on that form now too.

And a stats row that grew up

Across the top of your activities you now get total distance, total training time, average pace, total elevation gain, your average VO2max and your average age grade — all for whatever slice of time you are looking at.

And you can now choose that slice yourself. The fixed options are still there, but a date range picker sits next to them for when the question is "how did my last eight weeks go", which is a question fixed buckets can never quite answer. A km/mi toggle switches the whole row at once.

Calcpace is also plainly a running site now. Ride support had been half-present in the interface since the beginning, and it made every screen slightly vaguer than it needed to be — filters offering a type you never used, stats averaging two different sports. Rides no longer appear anywhere; nothing was thrown away. The maps got quicker too: the mapping library used to load on every page, including the ones with no map on them, and now loads only where there is a route to draw.