Hiking Time Calculator
Estimate how long a hike will take from its distance and elevation gain and loss, your walking speed, pack weight and breaks. Compare Naismith's rule with Tobler's hiking function and get a finish time and a safe turnaround time.
Last updated:
Naismith assumes 5 km/h (3.1 mph). Use 4 for a relaxed pace, 6 for a brisk one.
e.g. an hour before sunset
How to use the Hiking Time Calculator
- Enter the route distance and its total elevation gain and loss (from a map, app or guidebook).
- Choose the route type: whole loop, or one-way numbers for an out-and-back hike.
- Set your flat walking speed, pack weight and how many minutes of breaks you take per hour.
- Add a start time and a must-be-back time (such as an hour before sunset).
- Read the estimated time, the finish time and the latest time you should turn around.
How the hiking time is estimated
| Method | Formula | Notes |
|---|---|---|
| Naismith (1892) | time = distance ÷ 5 km/h + ascent ÷ 600 m/h | Imperial version: 3 mph plus 1 hour per 2,000 ft |
| Langmuir descent | −10 min per 300 m on 5–12° slopes; +10 min per 300 m above 12° | Uses the average descent angle of the route |
| Tobler (1993) | speed = 6·e−3.5·|slope + 0.05| km/h | Slope = rise ÷ run; fastest at about −5% |
The calculator splits the route into an uphill part and a downhill part in proportion to the elevation gain and loss, applies each method, then scales the result to your own flat walking speed (Naismith assumes 5 km/h). Pack factors of +10% to +30% and break time are added on top. These pack factors are practical rules of thumb, not a published standard.
Typical moving times (Naismith, 5 km/h)
| Distance | No climb | +300 m (≈1,000 ft) | +600 m (≈2,000 ft) | +1,200 m (≈4,000 ft) |
|---|---|---|---|---|
| 5 km (3.1 mi) | 1 h | 1 h 30 min | 2 h | 3 h |
| 10 km (6.2 mi) | 2 h | 2 h 30 min | 3 h | 4 h |
| 15 km (9.3 mi) | 3 h | 3 h 30 min | 4 h | 5 h |
| 20 km (12.4 mi) | 4 h | 4 h 30 min | 5 h | 6 h |
Planning tips
- Set a turnaround time before you start and stick to it, even if the top looks close.
- Plan to be back at least an hour before sunset; descending in the dark is slow.
- Groups move at the pace of the slowest hiker, and large groups take longer breaks.
- At high altitude, in snow or on scrambling terrain, allow much more time than any formula suggests.
Frequently asked questions
What is Naismith's rule?
Naismith's rule, proposed by Scottish mountaineer William Naismith in 1892, allows 1 hour for every 5 km (3 miles) of distance plus 1 hour for every 600 m (2,000 ft) of ascent. It gives moving time only, without breaks.
What are Langmuir's corrections?
Eric Langmuir refined Naismith's rule for descents: on gentle slopes of about 5 to 12 degrees, subtract 10 minutes per 300 m of descent; on slopes steeper than 12 degrees, add 10 minutes per 300 m, because steep downhill is slow and tiring.
What is Tobler's hiking function?
Waldo Tobler's 1993 formula estimates walking speed from slope: speed = 6 × e^(−3.5 × |slope + 0.05|) km/h. It peaks at about 6 km/h on a slight downhill of 5% and slows on steeper ground both up and down.
How long does it take to hike 10 miles?
On flat ground at 3 mph it takes about 3 hours 20 minutes of moving time. Add roughly 1 hour for every 2,000 ft of climbing and 10 minutes of breaks per hour, so a 10 mile hike with 2,000 ft of gain usually takes 5 to 5.5 hours in total.
What is a turnaround time?
A turnaround time is the latest clock time at which you head back, no matter how close the summit is, so you return before dark or bad weather. For an out-and-back hike it is your deadline minus the estimated return time.
How accurate are hiking time estimates?
They are starting points. Rough or rocky trails, snow, heat, altitude, group size and fitness can change times a lot. Compare the estimate with your own past hikes and adjust the flat speed until it matches you.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.