Back to Training Guides
Race Distance

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

Get a clear benchmark-driven answer for good 2K times, with conversion formulas, table views, and practical pacing structure.

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

What is a good 2k run time?

A good 2k time is 9:13. This is the average 2K time across all ages and genders. The fastest time in the benchmark dataset used for this page is 4:52.

Source context: benchmark snapshot from Run Regimen benchmark data and editorial policy, checked March 13, 2026.

Separate official-record context: World Athletics records listings. Official records update periodically, so treat the benchmark and official-record contexts as separate references.

Compliance note

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

Overall Benchmark

9:13

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

Male Benchmark

8:32

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

Female Benchmark

9:54

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

Fastest Benchmark

4:52

Fastest 2K time in the benchmark dataset snapshot.

How to interpret a good 2K time

A useful benchmark is contextual, not absolute. Age, event depth, terrain profile, and training consistency all affect outcome. Use benchmark tables as orientation, then combine them with your recent races and split quality.

Evidence reviews such as Joyner and Coyle and pacing synthesis from Abbiss and Laursen support this multi-factor view of distance performance.

Average 2K run time by age and ability

The benchmark section below provides age-row and ability-band context with finish-time, pace, and speed views. Values in pace/speed tabs are generated deterministically from the same finish-time table so the math is internally consistent.

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 2K Running Times

A good 2K time for a man is 8:31. This is the average 2K time across men of all ages. The fastest 2K time in this benchmark dataset is 4:52.

AgeBeginnerNoviceIntermediateAdvancedEliteWR
1014:1511:5510:128:568:005:49
1512:2010:198:507:446:555:02
2011:559:588:317:286:414:52
2511:559:588:317:286:414:52
3011:559:588:327:286:414:52
3512:0710:088:407:356:484:56
4012:3310:308:597:527:035:07
4513:0210:549:208:107:195:19
5013:3311:209:428:307:365:32
5514:0711:4810:068:507:555:46
6014:4312:1910:329:148:166:00
6515:2312:5211:019:398:386:17
7016:1013:3111:3410:089:046:36
7517:2314:3212:2610:539:457:06
8019:1416:0513:4612:0410:487:51
8522:0818:3015:5013:5212:259:02
9026:5622:3119:1616:5315:0711:00

Female 2K Running Times

A good 2K time for a woman is 9:53. This is the average 2K time across women of all ages. The fastest 2K time in this benchmark dataset is 5:35.

AgeBeginnerNoviceIntermediateAdvancedEliteWR
1015:4213:2111:3410:139:136:32
1514:0611:5910:239:108:165:52
2013:2511:259:538:447:525:35
2513:2511:259:538:447:525:35
3013:2511:259:538:447:525:35
3513:3011:299:578:477:565:37
4013:4711:4310:098:588:055:44
4514:1712:0810:319:188:225:56
5015:0112:4611:049:468:496:14
5515:5313:3011:4210:209:196:36
6016:5014:1912:2510:589:537:00
6517:5615:1513:1311:4110:327:28
7019:1116:1914:0812:2911:157:59
7520:3717:3215:1113:2512:058:34
8022:1918:5816:2614:3213:069:17
8525:0821:2218:3116:2114:4410:27
9030:1725:4522:1819:4317:4612:35

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 table

Find your age row, compare across ability columns, then switch to pace/speed tabs for execution context. Male and female sections use different benchmark source times, but the conversion formulas are identical across both sections.

Formulas used for pace and projection

Pace from finish time

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

Use this to convert 2K finish time into actionable pacing.

Speed conversion

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

Useful for treadmill translation and cross-unit planning.

Riegel projection

T2 = T1 * (D2 / D1)^1.06

Empirical projection model from Riegel (1981) for equivalent-distance planning.

Imperial pace conversion

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

Converts the same finish time to min/mile pace context.

Worked examples

Example 1: converting the overall benchmark

9:13 = 553 seconds

Pace (sec/km) = 553 / 2 = 276.5 sec/km = 4:37/km

Pace (sec/mile) = 553 / 1.24274 = 445 sec/mile = 7:25/mi

Speed = 13.02 km/h

Example 2: distance projection from benchmark anchor

Male age 30 intermediate benchmark = 8:32.

T2 = 512 * (5 / 2)^1.06 = 1,352 sec = 22:32 for 5K

Projection models are planning anchors, not guaranteed outcomes.

Practical pacing framework

First 600m

Start controlled and lock into sustainable rhythm early.

Middle 800m

Protect pace consistency and avoid abrupt surges.

Final 600m

Increase effort if stable, then finish with your strongest controlled push.

Common mistakes that distort comparisons

  • Comparing courses with different terrain and conditions without adjustment context.
  • Treating a benchmark table as an absolute rule instead of a descriptive distribution snapshot.
  • Using stale race anchors from a different training phase to set current targets.
  • Ignoring split quality and focusing only on finish-time headline numbers.

Frequently asked questions

Is 10:00 a good 2K time?

For many runners, 10:00 is a useful practical benchmark. To interpret it properly, compare against your age-row band and recent progression trend.

Why are benchmark and official best times different?

Benchmark tables show broad population distributions. Official records show single certified best performances. They are complementary, not interchangeable.

How should I pace 2K efforts?

Aim for controlled opening pace, steady middle section, and a progressive final segment. That pattern usually produces better consistency than an all-out first lap.

Can 2K be used to estimate 5K potential?

Yes. Projection models are useful planning anchors, but 5K-specific preparation still governs 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.