⏵ Guide · Free

How long does it take to run a 100 mile race?

Most people finish a 100 mile race in 24 to 30 hours. The fast runners go under 20 hours, strong amateurs are chasing the sub-24 hour buckle, and on the hardest mountain courses with 36 or 48 hour cutoffs, finishing past 30 hours is completely normal. The one thing that moves the number more than anything else is the course. A flat 100 and a 20,000-foot mountain 100 can be many hours apart for the exact same fitness. I will walk you through the finish times, the cutoffs, the pace each one needs, and how the terrain changes your real number.

⏵ At a glance

100 mile finish times and the pace each needs

Finish time	Average pace	Who runs it
Under 15 hours	Faster than 9:00 /mi	Elite and front of the field, usually on flatter, faster courses
15 to 20 hours	9:00 to 12:00 /mi	Competitive and very strong age-group runners
20 to 24 hours	12:00 to 14:24 /mi	Experienced runners chasing the classic sub-24 "one day" buckle
24 to 30 hours	14:24 to 18:00 /mi	The largest band of finishers on standard 30-hour mountain 100s
30 to 36 hours	18:00 to 21:36 /mi	Finishers on tougher courses with a 36-hour limit
36 to 48 hours	21:36 to 28:48 /mi	Back-of-pack finishers on the hardest mountain 100s with long limits

These paces are total averages across the full 100 miles, and that counts every climb, every aid station, every stop. Your moving pace has to be faster than the average to bank time against the minutes you lose walking and refueling.

What is the average 100-mile finish time?

There is no single official average, because every 100 is run on a different course in different conditions. The number you see most is around 28 hours, and the biggest band of finishers lands between 24 and 30 hours.

It depends entirely on the course

On a fast, flat, well-supported 100 like Rocky Raccoon, a lot more of the field comes in under 24 hours. Put that same runner on a high mountain course with 20,000-plus feet of climbing and they might finish five to ten hours slower, with a big chunk of the field using most of a 30 or 36 hour limit. A flat-course average and a mountain-course average are not the same number. So "average" only means something once you tie it to a specific race profile.

Western States is a good one to look at. In a recent year with good weather, about 86 percent of starters finished under the 30-hour limit, and roughly a third of those earned the sub-24 hour silver buckle. A big share of the rest came in during the final two hours, right up against the cutoff. That is the shape of most 100 mile finishes: a fast front, a thick middle, and a wave of people crowding the back of the clock.

Many runners do not finish at all

A 100 miler is hard enough that the did-not-finish (DNF) rate is a real part of the story. Across 100 mile races with a 30-hour cutoff, DNF rates have run from around 13 percent in great conditions to over 50 percent on hard courses in bad ones, and Western States has averaged roughly 27 percent over its history. So "how long does it take" comes with an honest second question: will you finish at all. Most of what moves both answers is pacing, fueling, heat, and how course-specific your training was.

Here is the good news though. Among runners whose first crack at a race was a DNF, most of them came back and finished it later. The 100 mile distance rewards a second try that is smarter and better paced.

Cutoff times: 24 vs 30 vs 48 hours

The cutoff is the wall the race builds around the clock. Most 100s give you 30 hours, the hardest stretch to 36 or 48, and sub-24 is a goal, not a limit. Each one turns straight into the average pace you have to beat.

Limit	Required average pace	Where you see it
24 hours	14:24 /mi average	A hard goal, not a cutoff. The classic sub-24 "one day" buckle
30 hours	18:00 /mi average	The most common 100 mile cutoff (Western States, Leadville-style)
32 to 36 hours	19:12 to 21:36 /mi average	Tougher mountain courses with more vert and technical trail
48 hours	28:48 /mi average	The most generous limits, on the highest, gnarliest courses

The intermediate cutoffs are what get people

The final cutoff rarely ends a race. The early and mid-race aid-station cutoffs do. A lot of courses set tight checkpoint times in the front and middle, so you cannot casually hike the first half and figure you will make it up later. You have to keep moving with margin from the gun, banking time on the runnable early miles without trashing your legs.

The fix is easy to say and hard to do: pull the official cutoff chart, build a pace plan that hits every checkpoint with a 30 to 60 minute buffer, account for the climbs between stations, and assume you will be slower late. A course-aware projection that splits the route segment by segment turns that from a guess into a real plan.

Predicting your finish, and the back-half fade

You cannot just double your 50 mile time. The back half of a 100 is slower, and how much slower comes down to how well you paced the front.

From a 50 to a 100

The rule of thumb most people lean on: your 100 mile time runs about 2.2 to 2.5 times your 50 mile time on a similar course, and closer to 3 times on a hard mountain 100 like Western States. A 10-hour 50 miler points you toward roughly a 22 to 25 hour 100 on comparable terrain, and 25 to 30 hours on something rougher. Treat the multiplier as a starting point, not a promise. Heat, sleep loss, fueling, and vert all push it around.

The more honest way is to grade-adjust for the actual course profile instead of just multiplying a flat time. That is the whole point of a course-aware finish projection. It reads your real fitness and the specific climb, descent, and footing of the race you are running, instead of pretending all 100 milers are the same.

How much the back half fades

Some slowdown is normal. Most finishers run a positive split, with the back 50 taking around 20 to 40 percent longer than the front 50. Here is the same 10-hour first 50 with a few different second halves:

Pacing scenario	Back 50	Finish
Even split (rare, very disciplined)	10:00	About 20:00
Mild fade (well-paced day, +20%)	12:00	About 22:00
Typical fade (most finishers, +40%)	14:00	About 24:00
Hard fade (went out too fast, +70%)	17:00	About 27:00

The lesson is not to avoid slowing down at all, it is to keep the fade small. Even or slightly negative splits are the ideal, because the time you "save" by going out fast almost always costs you more later. Bank patience early, eat consistently, and protect your quads on the descents.

Why terrain, vert, and aid stations change everything

This is where a generic flat pace chart falls apart. Two 100 milers with the same distance can finish hours apart, and the reason is what is under your feet and how much you climb.

Climbing is the single biggest variable

A rough running version of Naismith’s rule adds about 1 minute per 100 meters (about 330 feet) of climbing at the same effort. The catch is the descent. A moderate downhill only gives back about half of what the matching climb cost you, so a course with equal up and down is still slower than flat. Stack that across a 100 with 20,000-plus feet of gain and you are looking at hours of difference versus a pancake-flat race for the exact same fitness. The climbs are not really what get you. The descents are.

Technical footing, altitude, and heat slow you down even more and make the downhills harder to bank, because you cannot let gravity do the work when the trail is rocky and steep. That is exactly why a finish projection has to be grade-adjusted and course-specific. A flat pace chart hands you a comforting number, and the mountain quietly tears it up.

Aid stations leak time

It is easy to lose 10 to 15 minutes at a single aid station without noticing, and a 100 miler has 15 to 25 of them. That adds up to an hour or more of standing still, especially at the crewed and drop-bag stops late in the race when you are tired and slow. If your goal is sub-24 at 14:24 per mile, an extra hour standing around is roughly four minutes per mile you now have to claw back on the move.

The fix is a checklist and a habit: know what you need before you get there, get in and out, and eat while you walk out instead of standing there. Stopped time is the cheapest time to find in a 100, and it is the time most runners throw away.

⏵ Free calculators for your finish time

Stop guessing off a static pace chart. Run your real numbers through our free, no-signup tools, then let Summit Line tie them to your actual fitness and the exact course you are running.

See all free running tools →

Keep reading

A finish time is just the output of training, pacing, and fueling. These guides cover the inputs:

Want to see these finish-time ideas on a real, nasty course? Read our Angeles Crest 100 course guide and the Kodiak Ultra Marathons guide, two mountain 100s where vert and heat reshape the clock.

⏵ Get your real number

Stop guessing off a static chart. Summit Line reads your actual training and the exact course profile, then projects a grade-adjusted finish time, builds a fueling and pacing plan around the climb and the heat, and gives you cutoff-aware splits for every aid station so race day is rehearsed, not guessed.

Get started free →See it on a real 100 miler

100 mile finish time FAQ

What is the average 100-mile finish time?

There is no single official average, and the reason is simple: every course is different. The figure you see thrown around most is about 28 hours, and the large majority of finishers land somewhere between 24 and 30 hours. The fast people come in under 20 hours, strong amateurs are chasing the sub-24 hour "one day" buckle, and on the hardest mountain courses with 36 or 48 hour limits a finish past 30 hours is completely normal. Flatter, less technical races run faster. High-vert mountain 100s run much slower. So an "average" only tells you anything once you pin it to a specific course.

What are typical 100-mile cutoff times (24 vs 30 vs 48 hours)?

Most 100 mile races give you 30 hours, and that is the standard for races like Western States and Leadville. Sub-24 hours is usually a goal and a buckle, not a cutoff. Harder mountain courses push the limit out to 32, 33, or 36 hours to make room for the climbing and the technical trail, and the very hardest events go all the way to 48 hours. The cutoff is just telling you the average pace you have to beat: 30 hours is 18:00 per mile, 36 hours is 21:36 per mile, and 48 hours is 28:48 per mile. Always check the exact number on the official race site, because that one number sets your whole pacing plan.

What pace finishes a 100 miler under 24 hours, and under the 30-hour cutoff?

Sub-24 hours means a 14:24 per mile average across the whole 100 miles, and that counts every climb, every aid station, and every bathroom stop. To beat a 30-hour cutoff you need 18:00 per mile. Here is the part people miss: those are total averages, not your running pace. Your actual moving pace has to be quite a bit faster than that to bank time against the minutes you lose walking the climbs, refueling, and slowing down late. On a mountain course, get yourself well ahead of the raw cutoff pace through the first half, because the back half and the night are going to be slower no matter what.

How do I predict my 100-mile finish from my 50-mile time?

The rule of thumb most people use is that your 100 mile time runs about 2.2 to 2.5 times your 50 mile time on a similar course, and closer to 3 times on a hard mountain 100 like Western States. So a 10-hour 50 miler points you toward roughly a 22 to 25 hour 100, and 25 to 30 hours on tougher terrain. But the multiplier is only a rough gauge. Your real slowdown comes down to training, how disciplined you were with pacing, heat, sleep, and how much vert the course throws at you. The honest way to predict it is to grade-adjust for the actual course profile instead of just doubling a flat time, and that is exactly what a course-aware finish projection does.

How much should I slow down in the back half of a 100?

Some slowdown is normal, and you should expect it. Most finishers run a positive split, with the back 50 taking around 20 to 40 percent longer than the front 50. Stay disciplined and well-paced and you keep it near the low end. Go out too fast and you can blow the back half out by 50 to 70 percent or more. The goal is not to avoid slowing down entirely, it is to keep it small. Even or slightly negative splits are the ideal, because the time you "save" by starting fast almost always costs you more later. Bank patience early, eat consistently, and protect your quads on the descents, and the fade stays small.

How much time will I lose at aid stations?

More than you think. It is easy to drop 10 to 15 minutes at a single aid station and not even notice, and a 100 miler has 15 to 25 of them, so that adds up to an hour or more of standing still. The crewed and drop-bag stops late in the race are the worst offenders, because that is when you are tired and slow. If your goal is sub-24 at 14:24 per mile, an extra hour standing around is roughly four minutes per mile you now have to claw back on the move. Have a checklist, get in and out, and eat while you walk out instead of standing there.

How does course terrain and elevation gain change my time?

Enormously. Climbing is the single biggest variable. A rough running-adapted version of Naismith’s rule adds about 1 minute per 100 meters (about 330 feet) of gain at the same effort, and crucially the matching descent only gives back about half of that, so a course with equal up and down is still slower than flat. Technical footing, altitude, and heat slow you further and make downhills harder to bank. A 100 with 20,000-plus feet of climb can finish many hours slower than a flat 100 for the same fitness, which is why a flat pace chart will badly mislead you on a mountain course. You need grade-adjusted, course-specific numbers.

How do I clear every intermediate aid-station cutoff?

The finish cutoff is rarely what ends a race, the early and middle aid-station cutoffs are. Pull the official cutoff chart, then work backward: build a pace plan that reaches each checkpoint with a buffer, accounting for the climbs between stations and the fact that you will be slower late. Front-load your time bank on the runnable early miles without burning your legs, keep aid stops short, and treat each intermediate cutoff as a hard checkpoint you want to clear with 30 to 60 minutes of margin. A course-aware projection that splits the route segment by segment makes this concrete instead of guesswork.

This guide is for planning and training, and it reflects publicly available data and expert consensus on 100 mile finish times, which vary widely by course, conditions, and runner. Cutoffs and aid-station times change from race to race. Always confirm the exact cutoffs and course profile on the official race website before you build your pacing plan.