About
Behind RaceRecords
A masters-age road runner from the Netherlands. I race in min/km, log every result, and have a complicated relationship with my own race history. I built racerecords.run because the apps I had been using treated my history like a feed, and I wanted a record book.
Who I am
I race road, sometimes trail, mostly between 5K and the marathon. The masters tables started catching my interest a few years ago. The fastest absolute times of my life are getting harder to beat every year. I only started running at 35, so a few years of improvement may still be in there. Either way, age grading is the target that does not expire.
Why RaceRecords exists
Two things came up over and over.
The first is that absolute PRs harden. By forty most runners will not touch their 5K from twenty-five. Age grading is the only metric that stays beatable for the rest of a racing life.
The second is that most running apps headline the absolute time and bury the percentage. RaceRecords flips that. The percentage is the headline. The absolute time stays on the card, but the number that moves with you gets the real estate.
Beyond that, the maths had to be auditable. The methodology page shows the exact tables and a worked example. If a percentage looks wrong, the support page explains how to flag it.
What I write about
Field notes on age grading. How the tables are built. Where the gaps come from. What the headline number actually means once you split it by distance, age, and field depth. Sourced where I can source, quiet where I can’t. New pieces land on the blog.
Contact
info@racerecords.run for anything: bug reports, methodology questions, or feedback on a post. I read everything that comes in.