So how many miles is a 50k?
A 50k is 31.07 miles. More precisely, 50 kilometers converts to 31.0686 miles, using the standard 0.621371 miles per kilometer conversion. Round to 31.1 for pacing math and you will not be off enough to matter.
In race distances you already know, that is a marathon (26.2 miles) plus about 4.9 miles. On a 400-meter track, it is 125 laps. On a standard neighborhood loop of one mile, it is 31 laps and change. Most 50k courses are trail, most have some climb, and most will feel longer than the number suggests. That last point is the whole reason this post exists.
50k = 31.07 miles. 50,000 meters. 164,042 feet. 125 laps of a standard 400m track. Roughly a marathon (26.2 mi) + 4.9 mi. Typical finish times for a first-timer: 5 to 7 hours on a moderate trail 50k, 4:15 to 5:30 on a flat road 50k.
Why a 50k is not a marathon plus five miles
The math looks close. Marathon plus five miles, add an hour, done. In 15 years of coaching, the runners who trained a 50k like a slightly longer marathon are the same ones who walked the last 90 minutes in a fog and swore off the distance at the finish. The distance is not the hard part. Two other things are.
First, terrain. Most 50k races are on trail with real climbing. Even a modest 2,000 feet of vertical over 31 miles changes the demand on your calves, quads, and lower back in a way road marathoners are not prepared for. The descents pound your legs in a way flat road running does not train.
Second, time on feet. A 3:30 marathoner finishes in three and a half hours. On a rolling trail 50k, that same runner is out there for five hours or more. Past hour four, your gut gets picky about food and your form gets sloppy on tired connective tissue. Both cost you time. Both are trainable, but only if you build for them.
The mental piece flips too. In a marathon, the last 10k is the fight. In a 50k, the middle 90 minutes, roughly miles 12 to 22, is where most first-timers lose their race. They ran the early climbs too hard, ate too little, and now they are trying to hold on with an empty tank.
The base you need before you commit
The most common pattern I see: a runner finishes a marathon, feels great, signs up for a 50k eight weeks later. Almost always a mistake. Not because the fitness is not there. Because the connective tissue and the specific fueling and time-on-feet demands need a longer runway than eight weeks of top-off training.
Here is the base I look for before a first 50k build:
- 25 to 30 miles per week sustained for the eight weeks before the build starts
- A long run of at least 13 miles already comfortable, run on a similar surface to the race
- Six months of consistent running, meaning no more than one week off in a row across that window
- If the race is on trail: at least one day a week already on trail, not just as a novelty
Without that base, the plan below does not fit. You need a two-to-three month base phase first, then the 16-week build. That is not padding. That is the difference between arriving healthy and arriving with a stress reaction in your tibia. I would rather have an athlete run their first 50k one season later and finish strong than force it and DNF at mile 22.
Weekly mileage: what actually predicts a finish
Generic 50k plans say 30 to 40 miles a week at peak. That number is fine for a flat road 50k and light for a mountainous one. The honest answer is that peak mileage for a first-timer should land somewhere between 40 and 55 miles per week, held for four to six weeks in the middle of the build, with a strong long run every weekend.

The structure that works for most first-timers with a solid base:
| Weeks | Weekly volume | Long run | Goal |
|---|---|---|---|
| 1–4 (base extension) | 28–36 mi | 14–17 mi | Introduce trail and vert |
| 5–9 (build) | 36–48 mi | 17–22 mi | Long run + back-to-back |
| 10–14 (peak) | 44–55 mi | 22–26 mi | Race-specific fatigue |
| 15–16 (taper) | 36 → 22 mi | 14 → 10 mi | Freshen legs, hold fitness |
Two rules that matter more here than in marathon training. First, easy days must actually be easy. At 50-mile weeks on trail, a moderate easy pace is what breaks you. Second, the cutback week is not optional. Every fourth week, drop your weekly volume by 20% and swap the long run for a mid-length trail hike. Your connective tissue needs the reset even when your lungs do not.
The other thing worth saying out loud: the peak weeks feel harder than marathon peak weeks. Not because any single run is harder, but because you are running six days a week and your legs never feel fresh. That is the point. You are training your body to work on tired legs, because that is what mile 24 of a 50k demands.
The long run and the back-to-back weekend
Two workouts do 80% of the work in a 50k build. The long run and the back-to-back.
The long run is the same shape as a marathon long run, but longer and slower. You do not need to go 31 miles in training. The longest single run in a first-time 50k build should top out around 22 to 26 miles, run at conversational pace, on terrain that resembles the race. I have coached athletes to sub-6 finishes on a longest run of 24 miles. Total time on feet across the block matters more than one hero run.
The back-to-back is the ultra-specific workout that marathon training does not use. On peak weekends, you run a moderate-long run Saturday and a hard-but-shorter run Sunday. Something like 18 miles Saturday, 10 miles Sunday. Or 16 and 12. Two days of combined volume simulate the last third of a 50k without a single 30-mile run that takes two weeks to recover from. Four back-to-backs in the middle of a 16-week build is the sweet spot.
A generic 50k plan gives every athlete the same back-to-back weekends. In practice, some athletes recover well and can hold two of them a month. Others need three-week gaps to absorb them. Johnny watches your sleep, workout output, and how the second run of the weekend actually goes. If Sunday's run is flat, we back off before we accumulate a bad week. If Sunday feels strong, we push the next block. Static plans miss this. A coach does not. See how the week-to-week works.
Pacing, walk breaks, and the four-hour rule
Most first-time 50k runners start too fast. Not by 30 seconds a mile like in a marathon, but by a minute or more per mile in the first hour. Adrenaline plus aid stations plus the sense that "5 hours is a long time, I have room" adds up to a mile-5 pace you cannot hold at mile 25.
The rule I give: your goal 50k pace should feel embarrassingly easy for the first hour. Conversational. If someone next to you asks a question, give a full sentence back without breathing hard. If you cannot, slow down.
Walk the steep climbs. Not because you cannot run them, but because running a 12 to 15% grade costs three times the energy of power-hiking it for one or two positions gained. Even competitive ultra runners walk the steep stuff. The rule I use with athletes: walk any climb where your walking heart rate stays within 10 beats of your running heart rate at the same effort.
The four-hour rule: once you cross four hours, the race becomes damage control. Nothing new goes in your stomach that you have not tested in training. Nothing new goes on your feet. Manage. Do not race. That is where the mental piece of long-distance racing gets tested, and it is very different from a marathon finish.
Fueling for a five to seven hour effort
Marathon fueling is roughly 60 to 90 grams of carbohydrate per hour. In a 50k, the same range applies for the first three hours, then something new becomes true: most runners' guts stop tolerating pure sugar past hour four. This is where the "gel wall" comes from, and it is one of the most predictable reasons first-timers blow up in an ultra.

What actually works, in the order I coach it:
- First 2 hours: gels or sports drink, 60 to 80g carbs per hour. Same as marathon fueling.
- Hours 2 to 4: shift half your intake to real food. Boiled potatoes with salt, banana pieces, quarter PB&J sandwiches. Your gut needs a break from pure fructose or maltodextrin.
- Hours 4 and beyond: whatever you can actually eat. This is where broth, gummy bears, watermelon, and Coke earn their reputation. Salt matters more than carbs.
- Water and salt across the day: roughly 500 ml per hour of fluid, plus 400 to 800 mg of sodium per hour depending on the heat.
None of this can be figured out on race day. Every long run in the back half of your build should be a fueling rehearsal. Bring the food you plan to race with. Time the intake. Note what your gut hates on hour four. The athletes I coach who finish 50ks feeling good are the ones who wrote down what they ate every long run and refined it three or four times before race day.
What to do next
If you are 16 weeks out from your first 50k and you have the base, here is where I would start this week.
- Nail down the course profile. Vert, terrain, expected weather, cutoff times. Your training should mirror it. A flat road 50k trains differently than a 5,000 ft vertical mountain 50k.
- Get on trail once a week, minimum, starting now. If the race has climbing, one of your weekly runs is on hills, not flat.
- Schedule your four back-to-backs. Weeks 6, 9, 11, and 13. Put them on the calendar now, not the week before.
- Test your fueling on every long run past 14 miles. Log what you ate, when, and how your gut felt at hour three. Adjust.
- Add two 20-minute strength sessions per week, focused on posterior chain, calves, and single-leg work. The descents will punish you if you skip this.
A 50k finished well is a very different experience than one survived. The first-timers I coach who nail this distance almost always say the same thing at the finish: "That was hard, but it was never desperate." That is the goal. Not to grit through the last 10k. To arrive at the last 10k with enough left to actually run it.
Want a 50k build shaped around your life and your race?
Every 50k course is different, and every runner recovers differently. I write your paces, weekly mileage, back-to-backs, and fueling rehearsals into a plan rebuilt every week, calibrated to the actual race you are running and the actual week you are having. No templates. No guesswork.
Book a free intro callGet the next training note
One email when a new post drops. Pacing, plans, and the patterns I watch for. No spam, unsubscribe anytime.
