Time on Feet: Why Mileage Fails Ultra Runners
Time on Feet: Why Mileage Fails Ultra Runners¶
Your 18-mile long run on Saturday showed 2,600 feet of gain and took 3 hours 40 minutes. Your Garmin logged it as 18 miles. Your marathon training plan also called for 18 miles this week.
Those two 18-mile runs share almost nothing.
Same distance on paper. Completely different physiological demand. The marathon runner who ran 18 miles on flat roads at 9:15 pace spent about 2 hours and 45 minutes on their feet. You spent nearly an hour longer, absorbed thousands of feet of vertical stress, and burned through glycogen reserves that a road runner never touches in training. Both Strava profiles say "18 miles." Only one of those numbers is honest about what happened to your body.
If you've signed up for your first 50-miler or 100K and you're deep into a training block that expresses everything in miles per week, this post is going to explain why your long runs feel crushing even when the mileage "looks normal" -- and give you the exact hour targets that make a 50-mile training block legible.
The mile is a road running unit¶
Weekly mileage as a training metric was built for roads. The entire infrastructure of modern marathon training -- Pfitzinger's 55 MPW ladders, Daniels' mileage progression tables, Strava's weekly goal widget -- was calibrated on the assumption that a mile takes roughly 9 to 11 minutes and happens on flat pavement.
That assumption breaks the moment you step onto trail.
Here's a concrete comparison. Two runs, both 18 miles:
| Road 18-miler | Trail 18-miler (moderate vert) | |
|---|---|---|
| Pace | 9:15/mi | ~13:30/mi average |
| Total time | ~2 hrs 45 min | ~4 hrs 3 min |
| Elevation gain | ~500 ft | ~3,600 ft |
| HR minutes above Z2 | ~25 min | ~90 min |
Same number in your training log. Nearly 80 extra minutes on your feet. Three thousand feet of additional climbing that your quads and ankles absorbed. Glycogen depletion that pushes well past the two-hour mark that road runners treat as the boundary of hard long runs.
Miles measure distance. Ultras are won and lost by time. These are not the same thing.
When you structure your training around miles, you're measuring the wrong dimension of the work. And the further you get from flat, fast roads -- 50 miles, 100K, 100 miles -- the wider that gap becomes.
What 'time on feet' actually measures (and what it doesn't)¶
Time on feet is simple: cumulative hours the body spends upright and locomoting under load, regardless of pace. It's not "moving time" on Strava (which pauses at traffic lights). It's not elapsed time inclusive of aid station breaks in a race. It's the duration your musculoskeletal system is absorbing impact and your metabolic system is processing fuel.
Mileage tells you how far you went. Time on feet tells you what your body actually experienced.
What TOF captures that mileage misses:
- Glycogen depletion curves. The body can sustain high-intensity effort for roughly 90 minutes before glycogen becomes a limiting factor. Time on feet tracks how deep into that depletion curve your long runs take you. A 3-hour long run at easy trail pace pushes you well past the point where any road marathon training run leaves you. That's adaptation you need -- but mileage doesn't show you it happened.
- Connective tissue fatigue accumulation. Your tendons, ligaments, and fascia don't care about miles. They respond to cumulative time under tension. This is why ultra runners develop specific structural fatigue in their lower legs, hips, and feet that road runners almost never experience -- and why training by time builds a different kind of durability.
- Neuromuscular adaptation to prolonged effort. The coordination breakdown that happens late in an ultra -- the shuffling gait, the tripping, the flat-footedness -- is a neuromuscular failure, not a cardiovascular one. You train your way out of it with hours, not miles.
What TOF does NOT measure: intensity distribution, vert stress, or elevation gain rate. A 4-hour easy slog and a 4-hour workout covering the same terrain are both "4 hours on feet" -- they're not the same stimulus. TOF is a volume metric, not an intensity metric. For pacing zones and workout structure, you still need a separate framework.
One useful reference point: elite trail runners like Kilian Jornet and some of the best 100-mile performers in the world structure their training weeks almost entirely in hours. Their coaches set weekly totals in time, not distance. The runners in the top 10 at Western States finish in 14 to 17 hours. Finishing competitive 100-milers takes 24 to 32 hours. The race itself is a time event. Training should be too.
The conversion problem -- why your current mileage number is lying¶
Let's make this concrete. Your training plan calls for 45 miles this week. You're running trail with real vert. Here's what those 45 miles actually represent depending on terrain:
| Terrain | 45-Mile Week: Time | Elevation Gain | Road-Effort Equivalent* |
|---|---|---|---|
| Flat road (50 ft/mi) | ~7.5 hours | ~2,250 ft | 45 miles |
| Moderate trail (200 ft/mi) | ~10.5 hours | ~9,000 ft | ~54 miles |
| Vert-heavy trail (300 ft/mi) | ~12.5 hours | ~13,500 ft | ~58–60 miles |
*Using the coaching heuristic that 1,000 ft of climbing ≈ 1 additional flat mile of equivalent effort (conservative; some coaches use 2,000 ft = 1 mi).
The runner doing moderate trail has just done the physiological equivalent of a ~54-mile road week -- while their training log says 45 miles. The vert-heavy trail runner is approaching 60 miles of road-equivalent stress.
If you're coming from marathon training where 45 miles felt manageable, and you've kept that same mileage target moving into ultra training on trail -- you may already be significantly over-training relative to what your body is adapted to handle. The number didn't change. Everything else did.
This is the conversion problem. Mileage-based plans have no mechanism for capturing it. The moment vert enters the picture, the plan is lying to you by omission.
The fix isn't complicated. Stop anchoring to miles. Anchor to hours. Then the comparison between road and trail, flat and vert, collapsed from a hidden variable into an explicit one.
Distance-specific weekly hour targets¶
This is the part no other post gives you: the actual targets, by distance, for competitive amateurs training for completion and respectable time -- not elite podium finishes.
These ranges come from ultra coaching consensus (resources like Jason Koop's Training Essentials for Ultrarunning and Andy DuBois's work). Present them as training block targets, not single-week prescriptions:
| Race Distance | Base Phase (hrs/wk) | Peak Week (hrs/wk) | Road-Miles Context |
|---|---|---|---|
| 50K | 6–8 hrs | 10–12 hrs | ~40–48 road miles, but terrain-dependent |
| 50-mile | 8–10 hrs | 12–16 hrs | ~50–65 road miles equivalent |
| 100K | 10–12 hrs | 16–20 hrs | Varies so widely by terrain as to be meaningless |
A few things to notice:
The 50-mile jump is stark. Most marathon runners peak at 8 to 9 hours of training per week. That's right at the base phase floor for a 50-mile block, not the peak. The training volume required isn't a small step up from marathon preparation -- it's a different level of demand entirely.
The 100K peak range means 20 hours in your biggest weeks. That's 2 hours 51 minutes per day, every day, at the top end. Most people can't absorb that load without serious multi-year base building. This is why "I ran a marathon, I'll sign up for a 100K" so often ends in DNS or injury -- the volume gap is enormous and not visible in mileage terms.
If you're training for a 50-miler and your peak week is under 10 hours, your mileage number is probably hiding a training deficit.
Check your own training log. Not the miles -- the hours. Pull up your biggest training week. Add up the actual time in motion. Compare it to the peak week target for your race distance. That gap, if there is one, is what your plan isn't telling you.
How to restructure one week using hours as the anchor¶
You don't need to throw out your training plan. You need to re-read it in hours and adjust the sessions that are coming up short. Here's the process.
Start with Saturday. The long run is the anchor. Set its target duration first, in hours. Everything else fills in around it. If you're targeting a 14-hour peak week for a 50-mile build, and your long run is 5 to 6 hours, you have 8 to 9 hours left to distribute across the other six days.
Here's what a 14-hour peak week looks like when you build it from the long run outward:
| Day | Session Type | Target Hours | Notes |
|---|---|---|---|
| Monday | Rest / easy walk | 0–0.5 hrs | Active recovery only |
| Tuesday | Easy run | 1.5 hrs | True easy -- conversational pace |
| Wednesday | Workout (tempo or strides) | 1.25 hrs | The only quality session this week |
| Thursday | Easy run | 1.5 hrs | Same effort as Tuesday |
| Friday | Easy / rest | 0.75 hrs | Pre-long-run shakeout or off |
| Saturday | Long run | 5–6 hrs | Anchor session |
| Sunday | Easy recovery run | 1.5–2 hrs | Tired legs, deliberately slow |
| Total | ~13.5–14 hrs |
A few things this makes visible that a mileage-based plan obscures:
- Wednesday's workout is short in hours. 1.25 hours feels like "only 8 or 9 miles" to a mileage-brain runner. But it's a quality session with warm-up and cool-down, and it sits in a high-stress week. That's the right amount. More mileage "to hit the weekly number" usually means extending the workout -- which is exactly the wrong adaptation for ultras.
- Sunday isn't a recovery day, it's a running day. One to two hours of truly easy effort on tired legs is a specific adaptation for ultra running. Mileage-based runners often skip this because "I already ran 20 miles Saturday." Converting to hours makes the purpose clear: you're accumulating time on tired legs, not recovering.
- Friday is a non-event. 45 minutes or off. That's it. Mileage logic pushes runners to "add a few easy miles" here -- hours logic says no.
One more practical note: if your watch's planned activity uses distance, override it with a time cap instead. Nearly every current GPS watch supports "run for 5 hours" as a session target. Road runners often don't know this option exists because they've never needed it. For ultra training on trail, it's more useful than any distance target.
For the full five-metric weekly system that puts TOF in context alongside elevation gain, long-run percentage, ACWR, and subjective effort, the 5 Weekly Training Numbers guide covers all of it.
The three times mileage still matters¶
Miles aren't useless. They're just the wrong primary metric for trail and ultra training. There are three places where mileage still earns its place in your weekly review.
Bone stress injury monitoring. High absolute weekly mileage -- regardless of terrain -- correlates with bone stress injuries in the tibia, femur, and metatarsals. The impact forces that accumulate bone stress are partially time-dependent but also repetition-dependent. Very high mileage weeks (60+) carry elevated bone stress risk even when the hours look manageable. Keep mileage as a secondary check on impact volume, especially if you're adding road or track work to your trail base.
Cross-athlete conversation. "My training partner runs 60 miles a week" is a useful social sentence. "My training partner runs 14 hours a week" produces a follow-up question about terrain and pacing before anyone can compare notes. For casual comparisons across athletes and training philosophies, miles remain the common language. Accept that limitation rather than fighting it -- just don't let it shape your own training structure.
Road race goal-setting. If you're using your trail ultra base to also target a road half marathon or marathon PR, pace targets and race strategy still operate in miles per minute. Converting your training to hours doesn't break road race prep -- you'll need both lenses, and the road race is the case where mileage has genuine predictive value.
Outside these three contexts: organize your ultra training block in hours.
Tracking hours in NavRun¶
Restructuring around time only works if you can see the numbers clearly. Weekly mileage is prominent everywhere -- it's the default view on Strava, the headline number on most training apps, the figure most runners quote when someone asks how training is going. Time on feet is buried.
NavRun surfaces weekly time on feet as a first-class metric in the weekly training report -- not a detail inside individual activity splits, but an aggregated weekly number alongside vert and load data. The same dashboard that tracks your ACWR against the 0.8–1.3 safe zone also shows you whether your week hit the hour targets for your training phase.
If you've been pulling your training data into Strava and trusting the weekly mileage view, the NavRun analytics breakdown will show you what your weeks actually look like in hours -- and flag the weeks where the time target and the mileage target are telling different stories.
See your time-on-feet breakdown in NavRun ->
The number your next plan should lead with¶
Pick up any published ultra training plan. Almost all of them express weekly volume in miles. Some of the better ones add a weekly long run duration in parentheses. Almost none of them restructure the entire week around time targets -- because they were written by people who built their coaching frameworks on road running assumptions.
That doesn't make the miles wrong. It makes them incomplete.
When you look at your training this week, ask a different question than usual. Not "how many miles did I run?" Ask: "How many hours did I spend on my feet?" Compare that number to the target range for your race. If there's a gap, you've found the part of your training that wasn't visible before.
The miles will still be in your log. Let them stay there. But build your training blocks in hours -- and watch the Saturday long run start to feel like the right kind of hard instead of an unexplained crushing.