Back to Training Guides
Race Distance

What Is a Good 5K Time? Average 5K Benchmarks, Pace Chart, and Practical Examples

Get a clear, data-grounded answer to what a good 5K time looks like, with pace formulas, projection examples, benchmark tiers, and practical pacing guidance.

14 min read
Written by Run Regimen Editorial Team
Reviewed by Run Regimen Methodology Review
Updated March 12, 2026

What is a good 5k run time?

A good 5k time is 23:58. This is the average 5k time across all ages and genders. The fastest 5k time in the benchmark dataset used for this page is 12:51.

Source context: benchmark snapshot from Run Regimen benchmark data notes, checked March 12, 2026.

Separate official-record context: World Athletics currently lists open 5 km world records of 12:49 for men and 13:54 for women.

Compliance note

This article and linked tools are for informational and journaling purposes only. I am NOT a doctor.

Overall Benchmark

23:58

Average 5K time across all ages and genders in the benchmark dataset.

Male Benchmark

22:31

Average 5K time across men of all ages in the benchmark dataset.

Female Benchmark

26:07

Average 5K time across women of all ages in the benchmark dataset.

Official Open Records

12:49 / 13:54

Current World Athletics open 5 km records for men and women.

How to interpret a good 5K time

A useful 5K benchmark is contextual, not absolute. Age, event depth, route profile, weather, and training consistency all change what a strong result looks like in practice.

The benchmark tables below are descriptive tables, not physiological laws. Use them to orient yourself, then combine that context with recent race results, pacing consistency, and current training quality. Performance reviews such as Joyner and Coyle support that race outcomes depend on more than one metric alone.

Average 5K run time by age and ability

This benchmark section follows the source pattern shown in the attached reference: age rows, ability bands, and tabbed finish-time, pace, and speed views. The difference is that this version adds clearer source separation, internal conversion consistency, and notes that distinguish dataset benchmarks from current official records.

Benchmark Table Views

Switch between finish time, pace, and speed views. Every tab is computed from the same benchmark finish-time matrix so values stay internally consistent.

Accuracy note: `min/km` and `min/mile` are pace (time per distance). `km/h`, `mph`, `m/s`, `km/min`, and `mi/min` are speed (distance per time). The same conversion logic is used for both male and female sections.

Male 5K Running Times

A good 5K time for a man is 22:31. This is the average 5K time across men of all ages. The fastest 5K time in this benchmark dataset is 12:51.

AgeBeginnerNoviceIntermediateAdvancedEliteWR
1037:3931:2926:5623:3521:0715:22
1532:3527:1423:1920:2518:1713:18
2031:2926:1922:3119:4417:4012:51
2531:2926:1922:3119:4417:4012:51
3031:2926:1922:3219:4417:4012:51
3531:5926:4522:5320:0317:5713:03
4033:0927:4323:4320:4618:3613:32
4534:2528:4724:3821:3419:1914:03
5035:4729:5525:3622:2620:0514:37
5537:1631:1026:4023:2120:5515:13
6038:5332:3127:4924:2221:4915:52
6540:3833:5929:0525:2822:4816:35
7042:4335:4330:3426:4623:5817:26
7545:5538:2332:5128:4625:4618:45
8050:4942:3036:2231:5128:3120:45
8558:2848:5341:5036:3832:4823:52
9001:11:0859:2950:5444:3539:5529:02

Female 5K Running Times

A good 5K time for a woman is 26:07. This is the average 5K time across women of all ages. The fastest 5K time in this benchmark dataset is 14:44.

AgeBeginnerNoviceIntermediateAdvancedEliteWR
1041:2935:1630:3327:0024:2017:15
1537:1431:4027:2624:1421:5015:29
2035:2730:0826:0723:0420:4714:44
2535:2730:0826:0723:0420:4714:44
3035:2730:0826:0723:0420:4714:44
3535:4030:2026:1723:1320:5614:50
4036:2530:5826:4923:4221:2215:08
4537:4332:0427:4724:3322:0715:41
5039:3933:4329:1325:4923:1616:29
5541:5635:4030:5427:1824:3617:26
6044:2937:5032:4728:5826:0618:30
6547:2340:1834:5430:5127:4819:42
7050:4043:0537:2032:5929:4321:04
7554:2746:1840:0735:2731:5622:38
8058:5750:0743:2538:2234:3524:30
8501:06:2256:2648:5443:1238:5627:35
9001:19:5901:08:0158:5552:0446:5533:15

Important table note

The final WR column follows the source benchmark-table label for the best time at each age row. It should not be read as the current absolute open world record for the distance.

What do the running abilities mean?

Beginner

Faster than 5% of runners

A beginner runner has started running and has run for at least a month.

Novice

Faster than 20% of runners

A novice runner has run regularly for at least six months.

Intermediate

Faster than 50% of runners

An intermediate runner has run regularly for at least two years.

Advanced

Faster than 80% of runners

An advanced runner has run for over five years.

Elite

Faster than 95% of runners

An elite runner has dedicated over five years to become competitive at running.

How to use the tables

Find your age row, compare across the ability columns, then switch to the pace tabs if you want training or race-execution context. If your result sits between two bands, use both as a realistic range rather than forcing a single label.

Male and female sections use different benchmark source times, but every pace/speed tab is calculated from the same conversion formulas, so unit logic stays consistent in both sections.

Formulas used for 5K pace and projection

Pace from finish time

Pace (sec/km) = Finish Time (sec) / 5

Use this to convert any 5K finish time into an actionable pace anchor.

Speed conversion

Speed (km/h) = 3600 / Pace (sec/km)

Useful when you want to compare road pace with treadmill speed.

Riegel projection

T2 = T1 * (D2 / D1)^1.06

An empirical projection model from Riegel (1981) for estimating equivalent results at other race distances.

Pace conversion to min/mile

Pace (sec/mile) = Finish Time (sec) / 3.10686

This converts the same 5K finish time into imperial pacing language.

Worked examples

Example 1: converting the overall benchmark to pace

23:58 = 1,438 seconds.

Pace (sec/km) = 1,438 / 5 = 287.6 sec/km = 4:48/km

Pace (sec/mile) = 1,438 / 3.10686 = 462.9 sec/mile = 7:43/mi

Speed = 3,600 / 287.6 = 12.52 km/h

Example 2: turning a table value into a 10K planning estimate

Male age 30 intermediate benchmark = 22:32 for 5K.

T2 = 1,352 * (10/5)^1.06 = 2,818 sec = 46:58 for 10K

This is useful for planning, not certainty. Race-depth differences, terrain, and endurance durability still matter.

Practical 5K pacing framework

Kilometer 1

Start controlled, usually 2 to 4 seconds per km slower than target pace.

Kilometers 2 to 4

Lock the target pace with stable splits and low variability.

Final kilometer

Progress effort if stable and finish with the strongest split you can control.

Pacing and taper context: Abbiss and Laursen and Bosquet et al..

Common mistakes that distort 5K comparisons

  • Comparing a flat race to a hilly one without context.
  • Using a stale benchmark from a very different training phase.
  • Reading benchmark tables as guarantees instead of descriptive ranges.
  • Ignoring split quality and looking only at the final finish time.
  • Confusing a benchmark-dataset best time with the current official open world record.

Frequently asked questions

Is 30:00 a good 5K time?

For many recreational runners, 30:00 is a solid first benchmark. It is more useful as a starting point for progression than as a universal performance label.

Why do the benchmark tables and official record note use different numbers?

The age-and-ability tables are a labeled benchmark dataset snapshot, while the official record note reflects current governing-body open records. They serve different purposes and should not be merged into one figure.

What does the WR column mean in the tables?

In this benchmark system, the WR column follows the source table label for the best time shown at each age row. It is not the same thing as the current absolute open world record.

Should I use finish time or pace view?

Finish time is better for quick comparison. Pace views are better when you want to turn a benchmark into a training or race-day execution target.

Can I use a 5K result to estimate 10K or half marathon time?

Yes. A projection formula like Riegel is useful for planning, but it should be treated as a starting estimate rather than a promise of outcome.

Should I pace a 5K with even splits or a negative split?

Most runners execute best with a controlled first kilometer, stable middle splits, and a stronger final kilometer. That usually beats an aggressive start.

Which Run Regimen tool should I use after this guide?

Use the Running Performance Calculator for equivalent distances, the Pace Calculator for pace math, the VDOT Calculator for training anchors, and the Split Calculator for race-day execution.

References

Use your result in the right calculator

Move from benchmark reading to actionable pacing and training targets with these tools.

Training note: This page is an informational training and journaling reference. Use it for pacing context and trend tracking, not for medical decisions.

Editorial references

Apply this guide with a matching tool

Pair the guide with a calculator so the numbers turn into a specific pacing or training decision.