Your GPS watch says 24 minutes a mile for the last hike. Is that good? Bad? Average? The watch won’t tell you, and neither will the trailhead sign. It just gives you a number and leaves you to guess whether you’re slow or completely normal.
You’re not slow. 24 min/mi works out to 2.5 mph — dead center of what most hikers actually walk on decent trail. That’s the whole trick to reading a pace number: convert it to speed, then compare it against real bands, not against whatever a trail-running friend brags about.
The bands that actually hold up
We cross-checked these against the fitness speeds built into our own hiking time calculator — the same numbers Naismith used in his original 1892 rule, still the baseline almost every modern hiking-time model starts from.
| Hiker | Speed | Pace |
|---|---|---|
| New to hiking | ~2.0 mph (3.2 km/h) | ~30 min/mi |
| Average trail fitness | ~2.5 mph (4.0 km/h) | ~24 min/mi |
| Fit, experienced | ~3.0 mph (4.8 km/h) | ~20 min/mi |
| Mountain athlete | 3.5+ mph (5.6 km/h) | ~17 min/mi |
That’s it. Four bands, one table, and you can place yourself in ten seconds. Don’t overthink the gap between bands — 2.0 and 2.5 mph feels identical minute-to-minute and only shows up over a full day.
The catch: that’s flat, maintained trail only
Every number above assumes decent dirt underfoot. Put the same hiker on loose talus and the pace collapses, even though nothing about their fitness changed.
| Surface | Time cost | Average hiker’s real pace |
|---|---|---|
| Maintained trail | baseline | 2.5 mph / 24 min/mi |
| Rough mountain path | +20% | ~2.1 mph / 29 min/mi |
| Talus, scree, big steps | +35% | ~1.9 mph / 32 min/mi |
| Unbroken snow | +60% | ~1.6 mph / 38 min/mi |
This is why your pace on the boulder-hop below Half Dome’s cables feels nothing like your pace on the John Muir Trail’s flat meadow miles near Tuolumne, even at identical effort. Terrain isn’t a modifier you can eyeball — it roughly doubles your time between the best and worst surface on this list.
Turning a pace into a plan
Say you clocked that 24 min/mi on smooth trail last weekend and you’re eyeing a 7-mile route that’s mostly loose rock. Don’t just multiply 24 × 7 — that assumes flat dirt the whole way and you’ll blow your turnaround time.
Convert pace to speed first (60 ÷ pace = speed), apply the rocky-terrain factor, then multiply back out:
- Pace → speed: 60 ÷ 24 = 2.5 mph
- Rocky terrain: 2.5 ÷ 1.35 ≈ 1.85 mph
- Time for 7 miles: 7 ÷ 1.85 ≈ 3 h 47 min, moving time only
That’s almost an hour longer than the naive 24 × 7 = 2 h 48 min guess. On a short-daylight day, that hour is the difference between a calm descent and a headlamp scramble.
What pace doesn’t tell you
Steps are the other pace obsession, and mostly a distraction. A 5’8“ hiker’s stride runs about 2.35 ft, so 5 miles works out to roughly 11,250 steps — a real number, but not one that changes your turnaround decision the way terrain and gain do. Skip the step count for trip planning. Use it for bragging rights afterward, if at all.
Our distance & pace converter handles the pace-to-speed math above along with stride and step estimates, and once you add elevation gain the hiking time calculator folds Naismith’s climbing penalty in too — because a “2.5 mph pace” hiker on a route with 2,000 feet of gain is not a 2.5 mph day anymore.
Know your flat-ground number. Then stop trusting it the moment the trail turns to rock.