Ultra Running vs Marathon: What Changes¶
Past the distance, the course decides an ultra. Trail surface, climbing, the night and the time limit shape the day, so marathon pace tables stop working. You plan by hours and aid stations instead.
A 50K is 31.07 miles, about five more than a marathon. If that were the whole difference, you would add five miles to your long run and carry on. It is not the whole difference. Two 50Ks can be the same distance and different sports.
This is for anyone weighing a first ultra: a marathon or several behind you, a half you loved, or a year of reading race reports and telling nobody. Here is what changes, and what you can keep.
Is a 50K much harder than a marathon?¶
It depends on the course.
A flat, groomed 50K is a long marathon. You are on your feet for longer, you eat more, and you slow down in the last hours. A mountain 50K is something else. The Speedgoat 50K at Snowbird, Utah lists about 11,300 feet of climbing and a 13-hour limit. Same 31 miles. The climbs, the altitude and the footing take most of the day, and the distance is the smaller part of what you are up against.
Marathon courses vary too, but inside a narrow band. Almost all of them are paved, most are close to flat, and you can compare one to another by finish time. Ultra courses do not sit inside a band. Vert, surface, how technical the trail is, whether it is single track or jeep road, whether you finish in daylight: each one moves the finish by hours.
So the useful question is not "how many miles." It is "what is the course, and how long will I be out there." The answer to that second one is usually longer than a marathoner expects.
Why can't I use my marathon pace for an ultra?¶
Three reasons, and the first is not about fitness.
Pace stops meaning effort. On a road, the same pace on two days is the same work. On a trail you might run a smooth descent fast at an easy effort and crawl up a steep climb at a hard one. Both are right. The watch number is the course talking, not you. We went through the mechanics in trail vs road running pace.
Walking is part of the plan. On steep climbs, hiking is the efficient move, and runners at every level do it. A marathon pace table has no row for it. If your plan is a set of splits, the first big climb breaks the plan and you feel behind. You are not behind. The table was built for a different race.
The pace has to last. A marathon is built to hold one effort for a few hours. An ultra asks for a pace you could keep going on for much longer, and for a stretch of the day you will be moving slower than you ever do in training. Starting at your marathon effort is the common way to turn hour six into a walk to the next aid station.
Even the maths shows the split. The usual way to predict a longer race from a shorter one is the Riegel formula, which scales time by distance raised to a power. Riegel's validated range is up to the marathon, with an exponent of 1.06. NavRun's public race time predictor uses 1.06 for road distances and a higher 1.08 beyond 26.2 miles, because the road exponent under-predicts ultras. Its own FAQ calls extrapolating a short race to 50 miles or more "a rough ceiling at best", since vert, terrain, heat and nutrition decide the day.
Pacing and estimation tables were written for the marathon and the half. The ultra version never got written down for most runners. That gap is old and nobody chose it.
Do ultras use different training?¶
Some of it carries over and some of it changes.
What carries over. The aerobic base you built on the road works on the trail. So does knowing how to hold back early and run the second half on purpose. Marathon training taught you patience with a long build, and an ultra block needs the same patience.
What changes.
- Time on feet starts to matter more than mileage. A ten-mile trail run with climbing can take twice as long as ten flat miles. The body is loaded by the hours. See time on feet vs mileage.
- Back-to-back long runs. Two long days in a row teach you to run on tired legs, which is most of an ultra. The first 50K training guide has a 12-week structure.
- Climbing and descending. Descents load the quads in a way flat running does not. If the race has vert, the training needs vert.
- Hiking on purpose. Practise it. It is a skill, and it saves your legs.
- Eating while moving. In a marathon you can finish on what you carried in. In an ultra, food is part of the effort. Your gut needs training the way your legs do.
- The taper. It runs differently too. The ultra taper guide covers why.
If you have pain that does not ease, or you are coming back from an injury, talk to a doctor or physio before you build volume. A coach or a running-literate clinician is worth the money here.
How is an ultra finish time estimated?¶
Start with a number, then treat it as a range.
Step one: a baseline. A recent race time scales to a first guess with Riegel, as above. Fine for a flat, runnable course. Rough for anything with real climbing.
Step two: the course. Distance alone misses most of it. A common adjustment, Scarf's rule from a 2007 paper, treats every 1,000 feet of climbing as roughly half a mile of flat running. NavRun's in-app prediction uses that rule, and it compares the vert in your recent training with the vert in the race and warns when the gap is wide. The rule is a starting point. Surface and technical trail add more, and heat and altitude add more again.
Step three: the shape of the day. The single finish time is the smallest part of what you need. You want to know:
- When you reach each aid station.
- What the clock says when you get there.
- Whether you are in daylight or in the dark.
- How much room you have before a cutoff.
That is the part your crew needs as well. A crew planning around one wrong number spends the night in the wrong place.
So hold the estimate loosely. The estimate is a shape, and the day will redraw it. A long slow day is a big day, and it is allowed to be slower than the table said.
What you can keep¶
You have already shown you can train for months, taper, and hold something together for hours. None of that is wasted. The marathon taught you the build. The ultra adds hills, hours, food and the night.
If you want a first guess at a long race, the predictor takes one recent result and gives times from 5K to 100 miles. No account.
Start with one recent race. navrun.app/tools/race-time-predictor