This hiking time calculator estimates trail duration with Naismith’s rule — the 1892 standard still printed in mountaineering manuals: allow 1 hour per 5 km (or 3 miles) of distance, plus 1 hour per 600 m (2,000 ft) of ascent.

–

Naismith’s Rule: 130 Years Young

William Naismith published his rule in 1892 for Scottish hillwalking — an hour per three miles plus an hour per 2,000 feet of ascent — and it survives because it matches how human legs actually convert distance and climb into time. The metric form used here (5 km/h + 1 h per 600 m) prices the defaults at 3 hours for 10 km with 600 m of climbing: 2 hours of walking, 1 hour of climbing. Its enduring accuracy for a “reasonably fit party on a trail in decent conditions” is almost suspicious, and its failure conditions are equally well mapped: it assumes trails (off-trail/bushwhack travel can halve speed), modest packs, and daylight navigation — each violation has a traditional multiplier, folded here into a single fitness/group factor you set honestly.

The refinements worth knowing: Langmuir’s descent correction (subtract a little for gentle descents, add for steep ones — descending is not free time), Tranter’s corrections (a table that bends Naismith by fitness test results and fatigue over long days), and the modern guidebook convention of quoting times for the “average party” that embed exactly this arithmetic. What the estimate is FOR: daylight math (start time + estimate + stops vs sunset), turnaround decisions, and water/food planning. Treat it as the moving-time floor of your day, then layer stops on top — the party that plans 3 hours for the defaults and carries 5 hours of margin walks out in daylight; the party that plans 3 hours total tells a rescue story.

Worked Examples (Verified)

  • Defaults: 10 km ÷ 5 + 600 ÷ 600 = 2 + 1 = 3.0 h moving time.
  • Big day: 20 km with 1,200 m gain = 4 + 2 = 6.0 h before stops.
  • Imperial form: 8 miles with 2,400 ft gain = 8÷3 + 2400÷2000 = 2.67 + 1.20 = 3.87 h (≈3 h 52 min).

Hiking Time Discipline

  • Moving time ≠ day length: add rests (classic: 10 min/hour), meals, navigation checks and the summit half-hour everyone actually takes.
  • Elevation GAIN is cumulative (every up along the route), not summit minus trailhead — rolling trails hide hundreds of meters of extra climbing.
  • Descent isn’t free and isn’t symmetric: steep descents can be slower than the climb (Langmuir) — long descents deserve their own time budget.
  • Group speed = slowest member’s speed; the fitness factor is where honesty lives — heavy packs, altitude above ~2,500 m, heat and snow all push it above 1.2.
  • Set a turnaround time from the estimate BEFORE starting, and obey it regardless of how close the summit looks.

Related Tools

Frequently Asked Questions

How does Naismith’s rule work?

Time = distance ÷ 5 km/h + ascent ÷ 600 m/h (metric), or distance ÷ 3 mph + ascent ÷ 2,000 ft/h (imperial). It prices horizontal travel and climbing as separable costs at standard rates: a fit walker covers 5 km of trail in an hour, and climbs 600 m in an hour of dedicated effort. Example: 10 km + 600 m of gain = 2 + 1 = 3 hours of moving time. This calculator applies it with an adjustable group fitness factor.

Does the estimate include rest breaks?

No — Naismith gives moving time. Add stops separately: the traditional allowance is roughly 10 minutes per hour of walking for short breaks, plus meal stops on long days. A 6-hour Naismith day typically becomes a 7–7.5-hour trailhead-to-trailhead day. Daylight planning should always use the padded figure, and the turnaround rule (halfway by half your daylight) should use it too.

How do I handle descents?

Naismith ignores descent; Langmuir’s widely used correction subtracts ~10 minutes per 300 m of GENTLE descent (gradient between about −5° and −12°) and ADDS ~10 minutes per 300 m for steeper descents, where footing and knees govern. For a simple out-and-back summit, the descent of a moderate trail usually runs 70–85% of the ascent time — many parties simply apply the rule to the round trip distance and total gain and accept the built-in conservatism.

What fitness factor should I use?

1.0 = Naismith’s reasonably fit reference party on trail. Use 0.8 for a fast, light, experienced party; 1.2 for mixed groups, heavy overnight packs or very rough trails; 1.4–1.5 for beginners, children, snow, significant altitude or off-trail travel. The right factor is a safety decision, not a vanity one: plan to the slowest member’s realistic pace, because groups stay together (or should).

Is elevation gain just summit minus trailhead?

No — cumulative gain counts every uphill meter along the route, including re-climbing after dips. A trail that drops 200 m into a saddle and re-climbs it adds that re-climb to your legs’ bill — 200 m extra one-way, 400 m across a round trip, none of it visible in the net elevation difference. Route planners report “total ascent” for exactly this reason; use that figure, not the elevation difference, in the calculator.

How accurate is Naismith’s rule?

For its reference case (fit party, trail, moderate weather), guidebook experience puts it within ~±15% — remarkable for 1892. It degrades predictably: technical terrain, scrambling, river crossings, extreme heat/cold and altitude all slow real parties beyond it, which is what the fitness factor absorbs. Professional guides still cross-check GPS-era estimates against it because its errors are honest and usually conservative in the right places.

What is a good hiking pace?

On trail: 4–5 km/h on the flat is standard for fit adults (Naismith assumes 5), 3–4 km/h for loaded backpacking, with climbing rates of 300–600 m/hour depending on gradient and fitness. Children and mixed groups run slower — hence group factors. If your party sustains 5 km/h INCLUDING climbs, you’re not defying the rule; you’re mis-measuring the gain or the distance.

Is this hiking time calculator free?

Yes — free, instant, no sign-up. Enter distance in km and total elevation gain in meters for a Naismith moving-time estimate with an adjustable fitness factor.