What Is a Good 5K Time?

"Good" depends on how long you have been running, but the honest general answer is this: under 30 minutes is a genuine milestone for a recreational runner, and under 25 minutes puts you comfortably above average in most parkrun-style fields.

More useful than a verdict is knowing what each time actually requires.

What each time means in pace

Finish	Per km	Per mile	Speed
18:00	3:36	5:48	16.7 km/h
20:00	4:00	6:26	15.0 km/h
22:30	4:30	7:15	13.3 km/h
25:00	5:00	8:03	12.0 km/h
27:30	5:30	8:51	10.9 km/h
30:00	6:00	9:39	10.0 km/h
35:00	7:00	11:16	8.6 km/h
40:00	8:00	12:52	7.5 km/h

The round numbers make this easier than most race distances: a 25:00 5K is exactly 5:00/km, and a 30:00 is exactly 6:00/km. Work out your own with the pace calculator.

The benchmarks worth aiming at

• Finishing — the only one that matters first time out. Walk-run is a legitimate way to do it.
• Sub-30 — the first real milestone. Requires holding 6:00/km, which is a comfortable-but-committed effort for most people after a few months.
• Sub-25 — 5:00/km. Above average in most local fields, and usually the point where training has to become structured rather than just consistent.
• Sub-20 — 4:00/km. A serious club-runner time; a small minority of recreational runners get here.

Age and sex shift all of these considerably, and any table claiming otherwise is being sold to you. Compare against your own last time first.

What your 5K predicts

Pace decays as distance grows, so multiplying out is badly wrong — a flat extrapolation would turn a 20-minute 5K into a 2:49 marathon, which essentially nobody runs.

Riegel's formula accounts for the decay: T₂ = T₁ × (D₂ ÷ D₁)^1.06, where the exponent was fitted to real race results rather than assumed.

From a 25:00 5K:

Distance	Predicted
10K	52:07
10 miles	1:26:19
Half marathon	1:55:00
Marathon	3:59:47

From a 30:00 5K: 10K in 1:02:33, half in 2:18:00, marathon in 4:47:44.

Two caveats. The prediction is most reliable within about a threefold jump — a 10K predicts a half marathon well; a 5K predicting a marathon is extrapolating endurance you may simply not have built. And it assumes you have actually trained for the longer distance. Treat it as a ceiling on what is possible, not a forecast.

How to actually get faster

The most common mistake in amateur running is running every session at a moderately hard effort. It feels productive and produces less improvement than the alternative, with more injuries.

Roughly 80% of your weekly volume should be easy — conversational pace, where you could hold a conversation without gasping. That is where the adaptation happens: capillary density, mitochondria, aerobic base.

The other 20% is genuinely hard:

• Intervals — 400 m to 1 km repeats at or faster than 5K pace, with recovery between
• Tempo runs — 20 to 30 minutes at a "comfortably hard" threshold pace, roughly your one-hour race effort
• A long run — slower than everything else, building endurance

Running easy runs easy is the hardest discipline for new runners to accept, and the single change most likely to improve a 5K time.

Things that move a time more than fitness does

• The course. A flat, fast course is worth 30 to 60 seconds over 5K against a hilly one.
• Pacing. Going out too fast is the most common way to lose a minute. Even splits, or a slightly negative one, beat a fast first kilometre almost every time. The pace calculator's split table gives you a target for each marker.
• Weather. Above about 15°C, times start slipping. Heat costs more than most runners expect.

What to do with the number

The main thing a 5K time is good for is comparison with your own previous one. It is short enough to race often — every few weeks without much recovery cost — which makes it a genuinely useful measure of whether the training is working.