5K Pace Chart: Race Splits and Training Paces for Every Finish Time

You've got a 5K goal time and you want more than just a pace-per-km lookup — you want the training paces that go with it too. Most pace charts give you a number. This one gives you a plan. Below you'll find every finish time from 14:00 to 40:00 — per-km pace, per-mile pace, and your 1km, 2km, 2.5km (halfway), and 4km splits. I've also built in something I've never seen on another pace chart: a training pace derivation table matched directly to your goal finish time, covering easy pace, threshold effort, and interval pace. Use both together and you have everything you need — from the first training session to race day.

5K Pace Chart — Race Splits (14:00 to 40:00)

A word on GPS accuracy before you dive in: your GPS watch will almost certainly over-measure a road 5K by 50–200m — this is down to tangent error and signal drift through corners. The paces and splits in this table are calculated for the official 5km distance, not the GPS-measured distance. At 5:00/km pace, 150m of GPS over-reading equals roughly 45 seconds of phantom running. My advice to you is simple: use the official km markers as your ground truth on race day, not the pace reading on your watch. The highlighted rows (20:00, 25:00, 30:00) are the most-searched finish time targets.

From Race Pace to Training Paces — The Derivation Table

This is where a race reference becomes a training tool. I've derived the paces below using the Jack Daniels VDOT model — the same framework used in most structured running programmes. The key rule in plain language: your easy pace should feel genuinely conversational. If you have to pause mid-sentence to breathe, you're running too hard.

Here's how to read this table: if your goal 5K is 25:00, your easy runs should be at 6:45/km or slower — not 6:00/km. The single most common training error I see is easy running that is too fast, which means you never recover fully before your next quality session. Easy to understand. Easy to ignore. Don't ignore it.

To put these paces into a structured plan, see the 5K training plan and full training pace derivation guide.

What Is a Good 5K Time? Context by Age and Gender

Every pace chart gives you numbers. Very few give you context. Here's a reference table for performance bands by age and gender, based on RunningLevel data and standard athletics age-grading tables. Two coaching notes before you look at it: age-grading exists so that a 52-year-old's 28:00 can be fairly compared to a 30-year-old's 23:30 — both may represent equivalent relative performance. And "good" is relative to your training age, not your chronological age.

I've coached runners from 17:00 to 45:00 for the 5K. The ones who improve most reliably are those who benchmark honestly against their own age group — not against some abstract "good" standard driven by what they see online. See the age-graded 5K pace chart for the full age-graded performance breakdown.

Condition Adjustments — Heat, Humidity, and Course Profile

A pace chart is misleading without adjustment guidance. I've seen a sub-22 runner produce a 24:30 in 32°C and 90% humidity and consider it a failure. When I age-graded the performance for conditions, it was equivalent to roughly 22:15 on a neutral day. The adjustment isn't just about excusing a bad result — it's about calibrating your training load and race expectations correctly.

Heat (above 20°C / 68°F): add 20–30 seconds per km for every 5°C above 20°C. At 25°C, add 20–30 sec/km to your target pace. At 30°C, expect a 40–60 sec/km pace hit — meaning a runner targeting 25:00 should be aiming for 28:00–30:00 on race day and treating the result accordingly.

Humidity — use wet-bulb temperature, not air temperature alone: a wet-bulb reading above 21°C (69.8°F) warrants a revised goal. To estimate wet-bulb: temperature − (0.4 × (temperature − 10) × (1 − relative humidity/100)). Or use the practical heuristic: if it feels like a sauna at 7am before the race has even started, revise your goal downward. Running by feel and effort in those conditions will almost always produce a better result than chasing a number the weather has already made unreachable.

Course profile: for every 10m of net elevation gain per km, add roughly 30 seconds per km to your target pace. A course with 50m of total climbing spread over 5km adds 30 sec/km — or 2:30 to your finishing time. Importantly, downhill sections do not fully compensate: the aerobic cost asymmetry between uphill and downhill running means you pay more going up than you recover coming down.

For the full heat-racing framework, see the 5K racing in hot weather guide.

How to Use This Chart on Race Day

The GPS problem: GPS typically over-measures a 5K road course by 50–200m. This is down to two things: signal drift through buildings and trees, and tangent error — your GPS records the path your device physically took, including every non-tangent line through corners. On a certified 5K with multiple turns, that adds up. On a 2024 race I measured on a certified road 5K with a Garmin FR955, the GPS read 5.14km on a 5.00km course. At 5:00/km pace, that 140m of phantom running equals roughly 42 seconds of effort your finishing clock will not record. Pace by GPS alone and you'll run faster than intended without knowing it.

The practical fix: use the 1km official course markers as your pace checkpoints — the splits in the table above are your reference. Set your watch to manual lap mode keyed to your 1km target split; turn off auto-lap. When you hit marker 1, press lap and check the split. That's ground truth. The watch pace readout is not.

Planning a negative split: a negative split means running the second half (2.5km–5km) faster than the first. The 2.5km halfway split column in the table above is your key reference point. Target arriving at 2.5km 3–5 seconds behind your goal halfway split — conserve the effort — then progressively accelerate through km 3, 4, and 5. Most runners can't hold this discipline in km 1 because the adrenaline and crowd pull them faster. The ones who do almost always negative-split. For a full negative-split race plan built from your goal time, see the negative-split 5K race plan.

FAQ — 5K Pace Questions Answered

What 5K finish time should I target as a beginner?

30:00 is the most common first-race benchmark. 35:00–40:00 is realistic for runners who have been training consistently for 8 weeks from a non-running base. Both are legitimate targets — pick the one that represents a genuine effort, not a guaranteed walkover.

How do I convert 5K pace from miles to kilometres?

Multiply your min/mile pace by 0.6214. Example: 8:00/mile × 0.6214 = 4:58/km. Or use the pace chart table above — both columns are provided for every finish time from 14:00 to 40:00.

What counts as a good 5K time for my age?

See the age and gender performance table above. "Good" is context-dependent — a 28:00 by a 55-year-old woman is equivalent in age-graded terms to roughly 23:30 for a 30-year-old. Age-grading exists precisely to make this comparison fair. The age-graded 5K pace chart gives the full breakdown.

How much slower should I run in easy training than at 5K race pace?

90–120 seconds per km slower. If your 5K race pace is 5:00/km, your easy run pace is 6:30–7:00/km. See the training pace derivation table above — the easy pace column is the most important number on that table, and the one most consistently ignored.

How do I use a pace chart to set my GPS watch for race day?

Find your goal finish time in the table, note the 1km split, and set a manual lap alert for that time. Switch off auto-lap. Then at each official km marker, hit lap and check your split against the table. Official markers are ground truth; your GPS split is not.

Why does my GPS show a different pace than the course markers?

GPS measures the path your device physically travels, including signal drift and the non-tangent lines you run through corners. On a 5K course with multiple bends, this routinely adds 50–200m to the GPS-measured distance. At 5:00/km pace, 150m of GPS over-reading equals roughly 45 seconds of phantom running your finishing clock won't credit you for.

What is a negative split in a 5K and how do I plan for one?

Running the second half (2.5km–5km) faster than the first half. From the table: find your 2.5km halfway split, target arriving there 3–5 seconds behind that split, then progressively accelerate through km 3 to the finish. The discipline is holding back in km 1 — which is harder than it sounds when the crowd pushes you forward.

Some Other Pages You May Like