What your parkrun time actually says about your fitness
Every Saturday, a few hundred thousand people get a number. Most of them compare it to last week's. Here is what it can tell you when you read it properly — and what to do about it on Tuesday.
parkrun is the biggest running experiment ever run: a free, timed 5 km every Saturday morning, on hundreds of courses across Australia and thousands worldwide, with every result published by lunchtime. That makes a parkrun time the most common fitness number a runner owns — and one of the least understood.
The time itself is a poor measure. It is affected by the course, the weather, the crowd at the start and whether you meant it. Read the right way, though, it answers four questions most runners never get a straight answer to.
1. Where do you actually sit?
Comparing a raw 5K time across runners punishes everyone who is not 28 and male. Age grading fixes that. It expresses your time as a percentage of the world-record standard for your exact age and sex, so a 23:00 at 52 and a 19:30 at 28 can be compared honestly — and in that example they land within half a per cent of each other, both a little above 65 %.
The bands are the same everywhere:
- Under 50 % — building. Most newer runners start here.
- 50–60 % — a solid club runner.
- 60–70 % — local class. You win your age group at small events.
- 70–80 % — regional class.
- 80–90 % — national class.
- 90 % and up — world class.
Then there is the percentile: where that grade lands among a real population of race results. One thing worth saying plainly — everyone in that population already runs. Landing at the 50th percentile does not make you average among people. It makes you mid-pack among people who race.
The parkrun time calculator gives you both numbers from one time, your age and your sex.
2. What is the time worth at other distances?
A 5K measures your aerobic engine well. The models coaches use — Riegel's formula and the Daniels & Gilbert VDOT tables — turn that into an equivalent time at every distance. For a 25:00 parkrun, both land within a few seconds of 52 minutes for 10K, a little under 1:55 for the half and just under four hours for the marathon.
Those numbers are a ceiling, not a forecast. They assume you are as well trained for the marathon as you are for the 5K, which nobody is. The further the distance from the one you actually train for, the more the prediction drifts — always in the same direction, because marathon performance depends on long-run endurance that a 5K does not build or test. The race time predictor shows both models side by side, and the gap between them is the honest measure of how much depends on training you may not have done yet.
3. What paces should you be training at?
This is the question a parkrun answers best, and the one almost nobody asks it. The same aerobic index that predicts your races also prescribes your training paces — and for most runners the surprise is not the hard ones.
For that 25:00 runner the calculator gives an easy pace around 6:40 /km, a threshold pace a little over 5:15 and an interval pace around 4:45. The easy one is the shock. A runner who races 5K at 5:00 /km is usually running their "easy" days at 5:45 or so — a full minute too fast — which is why the hard days never feel sharp and the easy days never feel easy.
Easy pace is not a reward for the hard sessions. It is the pace that lets you absorb them. Get it right and everything else in the week improves; get it wrong and the week is three medium efforts and a tired Saturday.
4. Is it moving?
One parkrun is a snapshot. A series is a trend, and the trend is the number worth caring about. The honest way to track it is not the raw time — which drifts with the weather, the course and the company — but the aerobic index behind it, read off the best genuine effort in a rolling window. That smooths out a bad Saturday and keeps a good one.
If the index has not moved in two months of consistent running, the training is not asking the right question. Usually that means the easy days are too hard and the hard days are not hard enough, which is the same mistake from both ends.
What to do on Tuesday
- Run the calculator on your most recent honest parkrun. Write down the three training paces.
- Run your next easy run at the easy pace. It will feel slow. That is the measurement working.
- Put one threshold session in the week — twenty minutes at the threshold pace, or three lots of eight — and nothing harder.
- Race a parkrun flat out again in four to six weeks, not next Saturday. Then re-run the calculator.
That is the whole loop: measure, prescribe, train, re-measure. A training plan is that loop done for you, week after week, with the paces re-priced every time the number moves. It is what the Outrunr app is for.
Common questions
Is parkrun's own age grade the same as the one here?
Close, not identical. parkrun grades against its own 5 km tables; the calculator uses the open WMA road standards with the Fair age factors, so a grade can land a point or two apart. The bands — 60, 70, 80, 90 per cent — mean the same thing in both.
My parkrun is hilly or on gravel. Does that matter?
Yes, and the models cannot see it. A hilly trail parkrun can cost a minute or more against a flat road course, which is worth more than a year of ageing in the tables. If you have a time from a flat course or a road race, use that one.
Do I have to have run a parkrun?
No. Any recent, honest 5K effort does the job — a race, a time trial, a hard solo run on a measured route. What the models need is a genuine effort, not a training run.
How often should I race a parkrun flat out?
Every few weeks is plenty if you want it to be a measurement rather than a habit. Most of your Saturdays are better spent running it as the easy or steady session your week asks for. An all-out 5K is a hard session, and hard sessions are rationed.
parkrun® is a registered trade mark of parkrun Limited. Outrunr is not affiliated with or endorsed by parkrun. VDOT is a trade mark of its owner. Outrunr implements the published Daniels & Gilbert formula and is not affiliated with them.