Personalized Hiking Time Calculator

Use a completed hike to calibrate a Naismith–Langmuir estimate for a planned route. The result separates moving time, expected stops, and an optional planning buffer.

Your numbers
Choose the units used for both the completed and planned hikes.
Enter the total distance of a representative hike you completed under broadly similar conditions.
Use cumulative elevation gain rather than the difference between the start and highest point.
Enter cumulative elevation loss if you want to apply Langmuir’s descent correction.
Choose the dominant downhill gradient; select mixed or unknown to omit the descent correction.
Use recorded moving time with meal, sightseeing, and other stopped time removed.
Enter the full planned route distance.
Enter the planned route’s cumulative elevation gain.
Enter cumulative elevation loss for the planned route.
Choose the dominant downhill gradient or omit the correction when the descent is mixed.
Include expected meal, rest, photography, and other planned stops.
Add a user-selected margin for unfamiliar terrain, navigation, weather, or group delays.

What this calculator leaves out

  • This is a route-planning estimate, not a guarantee of pace, trail conditions, daylight, or safe completion.
  • The personal factor transfers best between hikes with similar terrain, weather, pack weight, altitude, fitness, and group composition.
  • The model excludes scrambling, river crossings, snow, route-finding delays, closures, illness, and changing weather; consult current maps, forecasts, land-manager information, and daylight times before setting out.

By using this calculator you agree to the Terms of Use. Results are estimates, not professional advice.

Buffered planning time7 hr 34 min

Personal pace adjustment
29.96%
Standard Naismith time
4 hr 29 min
Personalized moving time
5 hr 50 min
Estimated elapsed time
6 hr 35 min
Personalized overall pace
35 min/mi

Personal pace adjustment is positive when the completed hike took longer than corrected Naismith time and negative when it took less time.

Keep stopped time separate from moving time so meal, rest, and sightseeing time is not counted twice.

A personal factor transfers weakly between hikes with very different surfaces, weather, loads, or group sizes.

How to use this calculator

  1. Choose the unit system used for both the completed and planned hikes.
  2. Enter the completed route’s distance, cumulative ascent and descent, and recorded moving time.
  3. Choose a descent class only when one gradient type clearly dominates the route.
  4. Enter the planned route profile and the time you expect to spend stopped.
  5. Add a buffer, then use the buffered time alongside current conditions and a turnaround plan.

How this hiking time estimate is calculated

This calculator starts with a baseline route time, then adjusts that baseline using your moving time from a completed hike. It is useful when you know that a generic “average hiker” setting does not describe you or your regular group. The completed hike should have broadly similar trail surface, load, weather, altitude, and group size.

Distance is converted to kilometres and elevation to metres. For each route, the corrected Naismith time is N = D ÷ 5 + A ÷ 600 + c(L ÷ 1800), in hours. D is route distance in kilometres, A is cumulative ascent in metres, and L is cumulative descent in metres. The descent value c is zero for mixed or unknown descent, minus one for a mainly gentle 5–12° descent, and plus one for a mainly steep descent over 12°.

For the completed hike, the calculator divides actual moving time Ar by its corrected Naismith time Nr: F = Ar ÷ Nr. This is the personal pace factor. A factor above one means the completed hike took longer than the rule; a factor below one means it took less time. The planned route’s moving time is M = F × Np. Planned stopped time B is added only after that: E = M + B ÷ 60. Finally, the selected buffer Q gives P = E × (1 + Q ÷ 100).

What moves the result most

The completed hike’s moving time has a direct effect because it creates the personal factor. A short recording that accidentally includes a long pause makes the factor slow; a recording that excludes part of the route makes it fast. Cumulative elevation gain matters more than the difference between the trailhead and summit because rolling terrain can include much more climbing than the endpoint elevations suggest.

Use the mixed or unknown descent setting unless most downhill travel really falls in one class. The gentle descent adjustment can make a route look implausibly quick when descent data is large or incomplete, so the calculator omits that adjustment if it would make the route time nonpositive and flags the input. Steep descent adds time because downhill travel on a steep route can be slower rather than faster.

What this calculator leaves out

This is a route-planning estimate, not a prediction of safe completion. It does not model scrambling, river crossings, snow, loose rock, route-finding, closures, illness, changing weather, daylight, or an individual response to heat and altitude. Check current maps, forecasts, land-manager information, and daylight separately, and set an independent turnaround plan.

Worked example

Suppose a completed hike was 5 km with 600 m of ascent, no descent adjustment, and 3 hours of recorded moving time. Its Naismith time is 5 ÷ 5 + 600 ÷ 600 = 2 hours, so the personal factor is 3 ÷ 2 = 1.5, or 50% slower than the baseline.

For a planned 10 km hike with 600 m of ascent and 1,800 m of mostly gentle descent, the corrected Naismith time is 10 ÷ 5 + 600 ÷ 600 − 1,800 ÷ 1,800 = 2 hours. Personalized moving time is 3 hours. Add 30 minutes of planned stops for 3 hr 30 min elapsed, then add a 20% buffer for a buffered planning time of 4 hr 12 min. The personalized overall pace is 18 min/km.

Common questions

What is Naismith’s Rule?

Naismith’s Rule is a hiking-time estimate that combines distance with climbing. In this calculator, the base rule allows one hour for each 5 kilometres plus one hour for each 600 metres of cumulative ascent. It is a starting point, not a promise of arrival time.

Why calibrate a hiking estimate with a previous hike?

A recorded moving time captures some of the pace effects that a generic rule cannot, including your usual fitness, group rhythm, and typical rest-free travel speed. It transfers best when the completed and planned hikes have similar terrain, conditions, pack weight, altitude, and group composition.

Should I use moving time or total elapsed time?

Use moving time for the completed hike. Add planned meals, rests, photography, and other stopped time separately for the planned hike so those breaks do not distort the personal factor or get counted twice.

How do I find cumulative elevation gain?

Use the route’s total ascent or elevation gain from a map, GPS track, or route-planning service. Do not use only the difference between the lowest and highest point, because every repeated climb contributes to cumulative gain.

When does Langmuir’s descent correction apply?

Use it only if downhill travel is mostly gentle or mostly steep. Mixed terrain is better entered as mixed or unknown, which applies no descent correction. One route-wide descent class cannot accurately represent a route that contains substantial amounts of both kinds of downhill travel.

Can I use an out-and-back hike as the reference?

Yes, provided its recorded moving time covers the complete out-and-back route and you enter its total distance and cumulative elevation changes. Its usefulness still depends on how comparable it is to the planned route’s surface, gradient, weather, load, and group.

Put this calculator on your site

Paste the snippet below where you want the calculator to appear. It stays up to date automatically and links back here.

<iframe src="https://countfolk.com/embed/personalized-hiking-time-calculator/" title="Personalized Hiking Time Calculator" width="100%" height="640" style="border:0;max-width:44rem" loading="lazy"></iframe>