Average marathon time: what the numbers actually mean for your race.

What the average actually is

The most-cited number in this conversation is a global average around 4 hours 30 minutes. Break it apart and men finish closer to 4:20 and women closer to 4:50, with US races usually a few minutes slower than European city marathons. Those figures come from tens of millions of finish-line results tracked over the last two decades, which is a lot of data to hide behind a single mean.

Two things to notice before you do anything with that number. First, the average has drifted slower over the last twenty years, not faster. More people are running marathons, and more of those people are running their first one. Second, the median at a big-city marathon like Chicago or New York usually lands 10 to 15 minutes faster than the global average because those fields skew a little more experienced.

So the honest version of the answer:

• Global average, all comers: around 4:30.
• Men, all comers: around 4:15 to 4:25.
• Women, all comers: around 4:45 to 4:55.
• Big-city major: shave 10 to 15 minutes off the above.
• First-time marathoners: most finish between 4:30 and 5:30.

That is the last time you should think about the average. From here on, we treat you as an individual runner, not a bar on someone's chart.

Why the average is a bad goal

In 15 years of coaching, I have watched more than a hundred first-time marathoners pick a goal by reading a "what's a good marathon time" article and choosing whichever number felt vaguely respectable. About seven out of ten of them arrived at race day with a plan calibrated to a fitness they did not have.

The problem is not that runners are unambitious. The problem is that the average lumps together a 28-year-old former college soccer player, a 55-year-old who started running eight months ago, a returning marathoner two years off a knee surgery, and a very fit new mom running her first race back. Their 4:30s mean four different things. Averaging them gives you a number and takes away every piece of information that would help you train.

The runners who nail their first marathon almost never picked a goal from a benchmark article. They picked a goal from a recent race time, an honest look at how much they could train, and a coach or friend willing to say the number out loud. That is the sequence that works.

What is a "good" marathon time, actually

A good marathon time is one you earned. That is not a fortune cookie. It is a real definition, and it has three tests.

1. You trained for it. The time you ran is consistent with the miles you actually put in. Not the miles you meant to put in.
2. You paced it. Your second half was within 5 minutes of your first half. If you positive-split by 20 minutes, you did not run your marathon. You ran two races: one confident, one desperate.
3. You would sign up for the next one. A good time leaves you tired, satisfied, and curious about the next race. A bad one leaves you afraid of the distance.

By that definition, a 5:15 first marathon can be a great performance and a 3:45 first marathon can be a mediocre one. Time alone tells you almost nothing. Time compared to your training, your pacing, and your future intent tells you everything.

The published benchmarks are still useful as landmarks, not as goals:

Where you fit on that ladder is a function of miles you can absorb, years of consistency, and how well your training is structured. Not talent. Not vibes. Not what your friend ran.

How to set your own marathon goal

The cleanest way to pick a goal marathon time is to work backward from something you already ran. This is what a coach does on day one. It works because your recent race time already contains all the information the average never had: your training, your genetics, your terrain, your life.

The tool most coaches use is VDOT, a running-specific fitness score built from race time. Plug in a recent 5K, 10K, or half marathon and you get an estimated marathon time and a full set of training paces. If you have not run a race recently, run a 5K or a 10K four to six weeks into the block. That single data point is worth more than a hundred benchmark articles. If you want the deeper version, we wrote the full explainer on VDOT and how to use it.

Two rules for the projection:

1. Do not chase a VDOT-predicted marathon time you have not trained for. The number assumes marathon-specific mileage. If your peak week is 30 miles and the predictor is spitting out 3:35, the predictor thinks you are training like a 3:35 marathoner, and you are not.
2. Add a buffer for your first one. On a first marathon, most athletes should target their VDOT prediction plus 5 to 10 minutes. Race day punishes optimism at mile 20.

Once you have a target, everything downstream gets easier: easy pace, workout paces, race-week strategy. If you want a walk-through of the whole build, the marathon protocol we give first-timers lays it out.

Age-graded times: the fairer benchmark

If you want to compare yourself to anything, do not compare to the raw average. Compare to your age-graded time. Age grading takes your finish time and adjusts it against a reference standard for your age and gender. A 3:45 marathon at 52 is a different performance than a 3:45 marathon at 27, and age grading actually captures that.

Most race results pages will publish an age-graded percentage next to your finish time. Rough guide:

• Below 50%: completing the distance. First marathons often land here.
• 50 to 60%: steady amateur, consistent training.
• 60 to 70%: serious amateur. Structured plan.
• 70 to 80%: local competitive. Boston-qualifier territory for most ages.
• 80%+: regional and national level for masters. Rare and earned.

Age grading also gives older runners something the raw average steals: a fair mirror. I coach athletes in their 50s and 60s who run age-graded 75% marathons and outperform 30-year-olds running 3:15 on a raw clock. Same distance. Different truth.

What common goal-time patterns actually require

Here are the training profiles I typically see behind each landmark time. These are patterns, not prescriptions. Some athletes hit them on less; almost none hit them on much less.

Look at that table honestly. If your current peak week is 25 miles and your goal is sub 3:30, the goal is not wrong. It is just further away than one race cycle. That is fine. Most of my athletes chasing a big number get there in two or three well-run cycles, not one. If you are targeting Boston specifically, we wrote a full masterclass on qualifying.

What to do this week

You did not read this far for another benchmark. You read this far to walk out with a number. Here is the sequence, in order:

1. Find a recent race time. A 5K, 10K, or half from the last 8 to 12 weeks. If you have none, put a 5K on the calendar 3 to 4 weeks out.
2. Convert it to a VDOT-predicted marathon time. This is your ceiling if you train specifically for the marathon. Not your goal yet.
3. Look honestly at your training. How many miles a week can you actually run for the next 16 weeks? Not aspirationally. Actually.
4. Cross-reference the table above. If your training capacity matches the goal, you have a target. If it does not, adjust the goal down or push the race back.
5. Add 5 to 10 minutes for your first marathon. Race day will spend that buffer on your behalf.

That gives you a real number. Not the average of ten million strangers. A number that belongs to you, the training you are willing to do, and the race you are actually racing.

Written by

Coach Johnny Crain

2:12 marathoner. 4× US Olympic Marathon Trials qualifier. 4× NCAA national champion and 4× NCAA runner-up. Spoke at the RRCA National Convention. Founder and head coach at RunFitCoach, where he coaches every athlete personally.