Hiking Time Calculator
Estimate route duration with distance, ascent, descent, terrain, and planned breaks using a Naismith – Aitken – Langmuir planning model.
Route inputs
Uses 5 km/h on paths and 4 km/h on other ground.
Gentle descent reduces time; steep descent adds time.
Required. Enter 0.1 – 1,000 using a decimal point.
Required. Total elevation gain, not the highest altitude.
Required. Enter 0 for a route with no recorded descent.
Required; zero is allowed. Include planned rest and meal stops.
Live estimate
Estimated hiking time
3 h 37 min
Planning estimate including 30 minutes of breaks.
Moving time
3 h 7 min
Planning pace
18:07 min/km
Base terrain speed
5 km/h
Estimated hiking time is 3 hours 37 minutes.
Time breakdown
Horizontal travel
2 h 24 min
Ascent allowance
1 h 5 min
Descent adjustment
– 22 min
Break allowance
30 min
Calculation detail
| Component | Applied rule | Time effect |
|---|---|---|
| Horizontal travel | 12 km ÷ 5 km/h | 144.0 min |
| Ascent allowance | 650 m ÷ 600 m/h | 65.0 min |
| Descent adjustment | – 10 min per 300 m | – 21.7 min |
| Break allowance | Entered break time | 30.0 min |
| Estimated total | Sum of all time effects | 217.3 min |
A negative gentle-descent adjustment means the model assumes moderate downhill travel is faster than level travel. It is not a promise that the terrain is safe or runnable.
How to use the Hiking Time Calculator
What this calculator does. This tool estimates the elapsed time needed for a planned hike by combining horizontal travel, uphill effort, downhill conditions, and rest stops. It is designed for route planning: deciding when to start, checking whether a route fits available daylight, comparing two itineraries, or estimating a return time for a trip plan. It does not measure personal fitness, technical difficulty, weather exposure, navigation delays, pack weight, altitude illness, river crossings, snow, heat, or emergency margins. Treat the result as a structured baseline, then add conservative contingency time for real conditions.
When to use it. Use the estimate while preparing a day hike, checking a mountain route against sunset or transport schedules, comparing a maintained trail with an off-path alternative, or documenting an expected return time for someone who is not joining the hike. Mountaineering Scotland's guidance on route timing and Naismith's Rule explains why distance, ascent, surface, and the party's actual pace all matter.
How to calculate. The calculator opens with a complete demonstration route and a validated Excel workbook ready to download. To replace the example:
- Choose Ground conditions. Select “Paths, tracks, or roads” for a 5 km/h horizontal speed, or “Other or rough ground” for 4 km/h.
- Choose Going downhill. Use the gentle setting only for sustained descents around 5° – 12°; use steep for slopes over 12° where descent usually takes extra care.
- Enter Distance, then select kilometres or miles. Enter Ascent and Descent, then choose metres or feet. Changing a unit converts the current values rather than merely changing the label.
- Enter Break time in minutes or hours. Read Estimated hiking time, review the supporting results and the calculation table, then choose Download Excel to save the current model.
- Use Reset to clear the demonstration and all calculated content. Reset may disable Download Excel until every required route field contains a complete valid value again.
Input guide. Ground conditions is required and sets the horizontal base speed; rough ground raises the estimate because it reduces speed from 5 to 4 km/h. Going downhill is required and selects the Langmuir-style descent adjustment: gentle descent subtracts 10 minutes per 300 m, while steep descent adds the same amount. Distance is a required positive decimal from 0.1 to 1,000 km-equivalent; “12” is a realistic example. Do not paste scientific notation or a decimal comma such as “1,5.” Ascent and Descent are required nonnegative totals up to 30,000 m-equivalent; “650 m” for each represents a loop returning near its starting elevation. These are cumulative gains and losses, not summit altitude. More ascent always adds time. More descent reduces time under the gentle setting but adds time under the steep setting. Break time is required, may be zero, and accepts up to 10,080 minutes; “30 min” is the demonstration. Increasing it adds exactly the same amount to elapsed time.
Output guide. Estimated hiking time is the total planning estimate, including breaks. Moving time excludes breaks but includes terrain and elevation adjustments. Planning pace divides total elapsed minutes by route distance and is shown in the selected distance unit; it is an estimate, not a measured GPS pace. Base terrain speed shows the horizontal speed selected by Ground conditions. The summary pills repeat the current route distance, ascent, base speed, and descent mode. The Time breakdown reports Horizontal travel, Ascent allowance, Descent adjustment, and Break allowance. In the Calculation detail table, Component names each contribution, Applied rule shows the relevant arithmetic, and Time effect reports signed minutes. A negative descent effect is a model correction; a nonpositive moving-time result is rejected as an implausible route profile.
Worked example. The opening route uses paths, a gentle descent, 12 km distance, 650 m ascent, 650 m descent, and 30 minutes of breaks. Horizontal time is 12 ÷ 5 = 2.4 hours, or 144 minutes. Ascent adds 650 ÷ 600 = 1.0833 hours, or 65 minutes. Gentle descent subtracts 650 ÷ 300 × 10 = 21.67 minutes. Moving time is therefore 144 + 65 – 21.67 = 187.33 minutes. Adding the 30-minute break gives 217.33 minutes, displayed as 3 h 37 min. The planning pace is 217.33 ÷ 12 = 18.11 minutes per kilometre, displayed as 18:07 min/km.
Learn more. For safety planning beyond the formula, the U.S. National Park Service Trip Planning Guide recommends checking current conditions, weather, equipment, and emergency communication before departure.
How the hiking-time model works
Total time = distance ÷ terrain speed + ascent ÷ 600 m/h ± descent ÷ 300 m × 10 min + breaks
The core rule allows one hour for each 5 km of forward travel and one hour for each 600 m of climbing. The Aitken terrain correction lowers horizontal speed to 4 km/h away from paths, tracks, and roads. The downhill correction treats moderate descent as faster than level walking and steep descent as slower. All calculations are performed internally in kilometres, metres, and minutes, so switching units changes only the entered representation, not the physical route.
The approach is intentionally transparent and conservative in scope. It works best for ordinary hiking where distance and cumulative elevation are known. It becomes less reliable on technical scrambling, deep snow, loose scree, dense vegetation, river crossings, severe heat, high altitude, or routes with frequent navigation stops. The National Park Service Hike Smart guidance emphasizes adapting plans to weather, trail conditions, personal ability, and a backup plan.
Interpreting the estimate responsibly
Use the output as a minimum structured estimate, not as a deadline to beat. Groups generally move at the speed of the slowest member. Add contingency for children, unfamiliar terrain, heavy packs, photography, route finding, crowded sections, water collection, changing footwear, or any condition that makes the nominal terrain category optimistic. On an out-and-back route, record ascent and descent across the whole itinerary rather than entering only the outbound leg.
Before leaving, compare the estimate with daylight, weather, closures, transport times, and the condition of every participant. Tell a trusted person the route and expected return time, and turn back early when conditions deteriorate.