If you have ever stood on the start line of a parkrun wondering "what time should I actually aim for today?", you are not alone. Most beginner runners either go out too hard and blow up by kilometre three, or run so cautiously that they finish with too much left in the tank. A 5K time predictor solves that problem by giving you a realistic, maths backed projection based on a race you have already run.

This guide walks through how the prediction maths works, what counts as a good 5K time in the UK, the pacing strategy that consistently delivers a personal best, and the common mistakes that cost beginner runners a fair chunk of their finishing time. The interactive calculator part way down the page does the maths for you and spits out a five split race plan you can take to your next parkrun.

What a 5K time predictor actually does

A 5K time predictor takes a race time you have already run, at any distance, and projects what you could realistically run for 5 kilometres. The maths behind it is a formula called the Riegel formula, first published by Pete Riegel in 1981. It looks like this:

T2 = T1 × (D2 / D1)^1.06

In plain English: your new race time (T2) equals your old race time (T1), multiplied by the ratio of the new distance to the old distance, raised to the power of 1.06. The exponent of 1.06 is what makes the formula work. It accounts for the fact that as races get longer, your pace slows down slightly, because endurance becomes the bottleneck instead of pure speed.

An example. Say you ran a 10K in 55 minutes. To predict your 5K time, you would calculate 55 × (5/10)^1.06. That comes out to roughly 26 minutes 25 seconds. The formula does not know how fit you are, how well you slept, or whether the course is hilly. It just gives you a strong starting point based on the relationship between distance and pace.

Where the formula works best

Riegel is most accurate when you are predicting between distances that are within roughly a 4 times ratio of each other. So predicting 5K from a 10K result is reliable. Predicting 5K from a 1 mile time trial is also reliable. Predicting 5K from a marathon time is shakier, because marathon fitness depends much more heavily on fuelling, endurance, and pacing discipline than 5K fitness does.

The formula also assumes you are properly trained for the input race. If you ran a half marathon while underprepared and limping the last three miles, the formula will under predict your 5K time. Garbage in, garbage out applies here as much as anywhere.

UK average 5K times: where do you actually sit

Parkrun publishes anonymised finish time data from millions of UK runs each year, and it is the best dataset we have for working out what is normal at a beginner and intermediate level. The numbers below are drawn from parkrun's 2024 to 2025 UK average finish data.

The headline number worth remembering is 31 minutes. If you finish a parkrun under 31 minutes, you are running faster than the average UK parkrunner. If you finish in 25 minutes or less, you are in the top quarter of the field. If you can break 22 minutes you are firmly in the top 10 percent.

What counts as a "good" 5K time at each level

Good is relative. A 28 minute 5K is brilliant for someone who started running six weeks ago, and disappointing for a sub 20 club runner having an off day. Here is a more useful breakdown based on the parkrun community's informal medal thresholds.

Most beginners overestimate how fast a "good" 5K time is. They see elite runners on Instagram clocking sub 17 minute times and assume anything over 25 is bad. The reality is that breaking 30 minutes is a milestone worth being proud of, breaking 25 puts you ahead of three quarters of the parkrun field, and breaking 20 puts you ahead of around 95 percent of UK recreational runners.

Your 5K time predictor and pacing tool

The calculator below uses the Riegel formula to project your 5K time and then breaks it into five even kilometre splits, adjusted for a small negative split race plan. Move the slider, pick your input distance and pace preference, and the projection updates in real time.

The pacing strategy that actually works for a 5K

Once you have a projected time, the question becomes how to actually run that time on race day. There are three pacing patterns to choose from. Two of them are good. One of them is bad.

Positive split. You start fast and slow down. This is what almost every beginner does on instinct, because adrenaline pushes you out too hard. It is also the slowest of the three patterns, because the time you bank in the first kilometre costs you double when you blow up.

Even split. You run all five kilometres at the same pace. This works. It is the simplest plan and it is what most coaches recommend for first time racers.

Negative split. You run the second half slightly faster than the first half. Research from the Journal of Strength and Conditioning Research consistently shows negative split runners post faster overall times than positive split runners across distances from 5K to marathon. For a 5K, a small negative split of around 5 to 10 seconds across the whole race is the sweet spot.

The split by split race plan

This is the pacing plan the calculator above is built around, and it is what most experienced parkrunners use when chasing a personal best.

• Kilometre 1. Within 2 to 3 seconds per km slower than goal pace. Adrenaline will make this feel painfully slow. That is the point. You are letting the field stream past you because most of them are about to blow up.
• Kilometre 2. Settle onto goal pace exactly.
• Kilometre 3. Hold goal pace. This is the mental crux of the race. The pace feels harder than it should, but you are right on track.
• Kilometre 4. Lift by 2 seconds per km. You are now overtaking the people who went out too hard.
• Kilometre 5. Empty the tank. Lift by another 3 to 5 seconds per km for the final 800 metres.

Common pacing mistakes that cost beginners 1 to 3 minutes

If you have a projected time but never quite hit it on race day, one of these is almost certainly the reason.

The first kilometre sprint. Most beginners run their first kilometre 15 to 30 seconds too fast. That sounds small. It is not. The metabolic cost of overshooting your aerobic threshold early in a race is paid back at roughly double the rate later. A 20 second over pace in kilometre 1 typically costs around 40 seconds in kilometres 4 and 5.

Looking at the watch every 30 seconds. Watches lag, GPS drifts, and obsessive checking creates a stop start pacing pattern. Glance at your watch at each kilometre marker and trust your effort the rest of the time.

Not warming up. A 5K is short enough that your body never fully wakes up if you skip the warm up. Ten minutes of easy jogging plus a few short strides before the start can knock 20 to 30 seconds off your finish time.

Treating mid race like training. A 5K race effort is sustained 8 to 9 out of 10 effort. If kilometre 3 feels comfortable, you are running too slowly. The whole point of racing is that it should feel harder than your training.

Picking a hilly first race. If you are chasing a personal best, pick a flat parkrun. Bushy Park in London, Riverside in York, and Conkers in the Midlands are well known fast courses. A hilly course can easily add 60 to 90 seconds to a 5K time.

Race day strategy from waking up to crossing the line

The race itself starts the day before, not the moment the starter's whistle blows. Here is a stripped down race day plan that works for most parkrun timed efforts.

The day before. Easy 20 minute jog or rest. Carb at lunch, normal dinner, lay out your kit. Pin your barcode to your shorts if it is a parkrun.

Race morning. Wake up at least 2 hours before the start. Light breakfast of toast and banana, or porridge if you can stomach it. Coffee if you usually have one. Avoid trying any new food on race day.

60 minutes before. Travel to the course. Sip water but do not drink a litre.

20 minutes before. Start your warm up. Ten minutes easy jogging, then four to six short strides of 80 to 100 metres at goal pace or slightly faster. Then 5 minutes of light mobility, ankles, hips, shoulders.

2 minutes before. Position yourself realistically in the start funnel. If your projected time is 28 minutes, do not stand in the front three rows. You will be trampled by faster runners and then trample slower runners yourself.

The race. Run the five split plan above. Pass people in kilometres 4 and 5. Try not to get sucked into the early sprint.

Across the line. Walk for at least 5 minutes before sitting down. Light food within 30 minutes. Easy walk or stretch later in the day.

How Edge fits in

The predictor on this page tells you what time to aim for. The next question is how to actually get faster between now and your next 5K. That is where having a structured training plan matters.

Edge is a UK training app used by 17,000+ members. When you sign up, Edge builds an adaptive starting plan around your current fitness level, your goal, your equipment, and your weekly schedule. That includes 5K specific work like interval sessions, tempo runs, and easy aerobic mileage, alongside general strength and mobility built into every week.

If life gets in the way and you miss a session, Flexi Swap lets you move it around your week. If you want to ask "should I change my Saturday parkrun pace based on this predictor?", Edge AI adjusts your plan in under 30 seconds and lets you speak to coaches directly. Edge syncs with Strava, Garmin, Apple Watch, and Coros, so your runs land in your training history automatically.

One honest caveat. Use this predictor to pick a realistic 5K goal. Edge can build a training plan around that goal. Edge AI lets you ask about race pacing in 30 seconds. The lean voice prompts during runs tell you when intervals start and end and call out pace targets at key moments. But Edge does NOT coach you through the race in real time like a chatty audio coach would, and Edge does NOT automatically set your race pace from a predictor like this one. The pacing plan above you carry in your head, or on a watch face. The training that gets you there is what Edge handles.

Frequently asked questions