A hiking time calculator exists because the obvious method — distance divided by walking speed — fails badly in hills. Two routes of identical length can differ by hours, and the variable that separates them is vertical, not horizontal. A time estimate that does not take ascent as an input is not an estimate at all.
Arb Digital publishes a free tools library, and this page sits in its sports section. It is deliberately different from the running pace calculator, which converts between pace, time and distance for a runner on a measured course: that tool has no field for elevation because road running does not need one. Hiking time is driven by ascent, descent gradient and load, so this page takes those as primary inputs and treats horizontal distance as only one component of the answer.
What This Hiking Time Calculator Does
It starts from Naismith's rule, the oldest and still the most widely used hill-walking time estimate, then applies three corrections that Naismith himself never made.
The first is Langmuir's descent correction, which recognises that going down is not simply the reverse of going up. On easy gradients descending is genuinely faster than flat walking, so time comes off. On steep, loose or wet ground it is slower than climbing, so time goes on. The selector decides which.
The second is a load penalty. Naismith's figures describe a walker carrying almost nothing. A multi-day pack changes the arithmetic substantially, particularly on ascent, and the tool applies a percentage per kilogram that you control.
The third is a fitness and party multiplier, playing the role that Tranter's correction table plays in the classic method. A group moves at the pace of its slowest member with the largest pack, and that is usually well off Naismith's assumed fit walker.
Finally it adds a break allowance and converts everything into a finish time, because the number that actually matters on a short winter day is not how long the walk takes but whether you get back in daylight.
How to Use It
- Take distance from the route, not the map's scale bar. Straight-line measurement understates a switchbacking path badly. Mapping software that follows the trail is what you want.
- Use cumulative ascent, not net height gain. A ridge walk that drops 80 metres into every col and climbs back out can easily double the figure you would read off the summit height.
- Set the descent gradient honestly. This is the input people get wrong. If your descent involves scree, boulder fields, wet slabs or a long series of big rock steps, it is steep, and the correction should be adding time.
- Pick the fitness multiplier for the group, not for you. If you are walking with others, the party moves at the slowest sustainable pace.
- Check the finish time against sunset. That comparison, not the total duration, is the safety-relevant output.
The Formula / How It's Calculated
Naismith's rule allows one hour for every 5 kilometres of horizontal distance, plus one additional hour for every 600 metres of ascent. In imperial terms that is one hour per 3 miles plus one hour per 2,000 feet. Written out: base minutes = (distance ÷ 5) × 60 + (ascent ÷ 600) × 60 with distance in kilometres and ascent in metres.
Langmuir's descent correction then adjusts for the way down: subtract 10 minutes for every 300 metres of descent on gentle to moderate gradients, or add 10 minutes for every 300 metres of descent on steep ground. The two directions of that correction are why the descent figure in the result grid can be negative.
After the corrections, the tool multiplies by the pack penalty — 1 + (pack kg × penalty per kg ÷ 100) — and then by the fitness multiplier. Breaks are added last as minutes per hour × walking hours, so that the allowance scales with the length of the day rather than being a flat figure.
Worked example, matching the values this page loads with. A 12 km route with 700 m of ascent and 700 m of gentle descent, an 8 kg pack, average party fitness and 5 minutes of breaks per hour. Distance time is (12 ÷ 5) × 60 = 144 minutes. Ascent time is (700 ÷ 600) × 60 = 70 minutes. That is 214 minutes of Naismith base. The gentle descent correction removes (700 ÷ 300) × 10 = 23.3 minutes, giving 190.7. The pack penalty is 8 × 0.5 = 4%, so 190.7 × 1.04 = 198.3. The average-fitness multiplier of 1.25 gives 247.9 minutes of walking. Breaks add (247.9 ÷ 60) × 5 = 20.7 minutes. The total is 268.5 minutes, or 4 hours 29 minutes — starting at 09:00, you are back at about 13:29.
Why Ascent Dominates Everything
Naismith's exchange rate is the most useful number in hill walking: 600 metres of climbing costs the same time as 5 kilometres of flat walking. Put another way, every 120 metres of ascent is worth a kilometre.
Once you internalise that, route choice changes. A 14 km path with 300 m of ascent and a 10 km path with 900 m of ascent look very different on a map, but they take almost exactly the same time — 10 km plus 900 m converts to an effective 17.5 km, against 14 km plus 300 m at an effective 16.5 km. The shorter route is the slower one.
It also explains why hill walkers talk in "equivalent flat kilometres" and why guidebook times for routes of the same length vary so widely. The one genuine caution is that the exchange rate is not constant: it holds reasonably on sustained moderate gradients and breaks down on very steep ground, where you are effectively scrambling and horizontal progress nearly stops.
Where Naismith's Rule Quietly Fails
The rule dates from 1892 and describes a fit walker on a good Scottish hill path. Four conditions break it, and none of them appear as inputs on most calculators.
Terrain underfoot. Deep heather, peat bog, boulder fields, soft sand and unconsolidated snow can halve your speed with no change in distance or ascent. There is no correction that reliably captures this, which is why local knowledge beats any formula on rough ground.
Navigation load. In cloud, or off a marked path, time disappears into stopping, checking bearings and pacing. The Mountaineering Scotland introduction to mountain navigation covers the timing and pacing techniques used for exactly this, and any route where you expect to need them will run well over a Naismith estimate.
Group size. Time lost to regrouping, layer changes and stops scales with the number of people, not the distance. Beyond about six walkers, add a meaningful allowance that the fitness multiplier alone will not cover.
Fatigue. All these rules are linear, and human performance is not. Hour eight of a long day is far slower than hour two, so long routes are systematically underestimated. If your total exceeds about six hours, treat the answer as optimistic.
Planning Around Daylight, Not Duration
The single most common way a hill day goes wrong is a route that was achievable but started too late. The finish-time output exists for that reason: it converts an abstract duration into the concrete question of whether you will be descending in the dark.
Two habits make the estimate safer. First, add a contingency rather than trusting the number — a common approach is to plan for the estimate, carry for the estimate plus half, and set a turnaround time you will honour regardless of how close the summit looks. Second, identify escape routes in advance, so that running late has an option other than continuing. The US National Park Service sets out the broader planning framework in its Hike Smart guidance, which covers knowing your limits, leaving a trip plan with someone not on the walk, and carrying the ten essentials.
On the physiological side, the walking calorie calculator gives you the energy cost of the day and the water intake calculator helps size the fluid you need to carry — which then feeds straight back into the pack weight field above, since water is usually the heaviest thing in the bag.
Arb Digital builds fast, dependency-free calculators and interactive tools that load instantly, rank in search and keep visitors reading.
Browse the Free Tools Talk to Arb DigitalCommon Mistakes to Avoid
- Entering net height gain instead of cumulative ascent — an undulating route can have twice the climbing its summit height suggests, and this is the single biggest source of underestimates.
- Calling a rough descent gentle — the correction flips sign, so a steep descent misclassified as easy can put your estimate out by nearly an hour on a big day.
- Using your own fitness for a group walk — the party moves at its slowest sustainable pace, and that is the pace the multiplier should describe.
- Forgetting that breaks scale with the day — a flat 20-minute lunch allowance is fine on a three-hour walk and badly short on a nine-hour one.
- Trusting a linear rule on a very long route — fatigue is not linear, and anything beyond about six hours will run over the estimate.
Related Free Tools From Arb Digital
The walking calorie calculator covers energy expenditure on foot and the water intake calculator covers hydration planning. The steps to miles calculator converts a step count into distance if that is how you track walks, and the running pace calculator handles pace, time and distance on flat measured routes where elevation is not the constraint. Everything else is in the free online tools hub.
Frequently Asked Questions
An 1892 hill-walking estimate allowing one hour for every 5 kilometres of horizontal distance plus one extra hour for every 600 metres of ascent. In imperial units that is one hour per 3 miles plus one hour per 2,000 feet of climbing.
Reasonable for a fit walker on good paths at moderate gradients, and progressively less reliable as terrain gets rougher, the party gets larger or the day gets longer. Treat it as a planning figure with a contingency, not a schedule.
Because on steep, loose or wet ground you cannot stride out and are placing every foot deliberately. Langmuir's correction subtracts ten minutes per 300 metres of gentle descent but adds ten minutes per 300 metres of steep descent, which is why the descent figure can be negative or positive.
Enough to matter, mostly on ascent, but there is no single agreed figure. This tool applies a percentage per kilogram that you set, defaulting to a modest half a percent, and you can set it to zero to leave load out of the calculation entirely.
Total cumulative ascent, adding every rise on the route. A ridge that repeatedly drops into cols and climbs back out can have well over twice the ascent that the difference between start and summit implies.
Because a pace calculator solves the relationship between pace, time and distance on a measured course and has no elevation input. Hiking time is dominated by ascent, descent gradient and load, so those are the primary inputs here and horizontal distance is only one term of several.
Yes. Switching the units selector converts your entries internally, so distance is read in miles and ascent and descent in feet, while the underlying Naismith and Langmuir constants stay the same.
This tool produces a planning estimate for general fitness and route-planning purposes. It is not mountain safety advice and cannot account for weather, terrain conditions or your own capability on the day. Responsibility for a route decision rests with the party making it.
