JoseFitani
✈️ Travel Planning

Hiking Time Calculator

Estimate hiking time using Naismith's Rule: 1 hour per 5 km plus 1 hour per 600 m of ascent.

This page explains how the hiking time calculator works, the data and formulas behind it, and how to interpret the result. Average speeds are empirical guidelines: walking 5 km/h, cycling 18 km/h, city driving 30 km/h, highway driving 90 km/h, train 120 km/h, airplane 800 km/h. These values are accurate to within about 20% for typical trips. The tool is one of 329 free, open tools on JoseFitani for maps and geography. It runs in your browser with no sign-up needed. Use the search field or click the map to drop a pin - the tool uses great-circle distance divided by mode-specific average speeds and returns the result in seconds. Below you'll find a step-by-step guide, real use cases, the methodology, FAQs, and data sources.

Important notice

Hiking times are rough planning estimates based on standard formulas. They are not safety advice. Always check current trail conditions and weather, tell someone your plans, and carry appropriate gear, food, and water.

Duration
1 h 7 min
Distance
100 km
62.1 mi
Average speed
90 km/h

How to use this tool

1
Enter your input

Type your query, paste coordinates, or click on the map. The tool uses great-circle distance divided by mode-specific average speeds to process your input locally in the browser.

2
View the result

The result appears instantly with the map showing your location. You can adjust by clicking elsewhere or searching a new place.

3
Copy or share

Click Copy to save to clipboard, or Share to send a direct link with the exact inputs.

What people use this tool for

Planning daylight-safe itineraries

Hikers can check whether a planned route fits inside available daylight before committing to it. Naismith's Rule converts distance and ascent into hours, which you then compare against sunset time minus a safety margin. Routes that fail this test get shortened or moved to a longer day.

Example: A group hiking in the Lake District checks a 14 km route with 700 m of ascent and realises it needs nearly five hours — too long for a 3 pm start in October.
Briefing mixed-ability groups

Walk leaders can give every participant the same time estimate so slower walkers are not surprised and faster walkers know when to expect regroup points. Naismith's baseline assumes a fit adult, so leaders add explicit margin for beginners, children, or heavy packs. A shared estimate prevents the group splitting under pressure.

Example: A club leader in the Scottish Highlands quotes Naismith's time plus 50% for a beginners' outing so nobody feels rushed on the ascent.
Comparing alternative routes

When two paths reach the same summit, the calculator shows which is genuinely quicker rather than which merely looks shorter on the map. A short steep route often loses to a longer gentle one once ascent time is counted. The comparison takes seconds and settles route debates with numbers.

Example: Two friends compare a direct 6 km scramble with 900 m of climb against a 10 km ridge walk with 400 m, and pick the ridge as the faster day.
Pacing multi-day treks

Trekkers stringing together several days can estimate each day's walking time to place camps and resupply stops sensibly. Consistent daily estimates reveal which day is the crux before you are living it. Building in a rest or short day after the hardest one keeps the whole itinerary achievable.

Example: A trekker on the Tour du Mont Blanc route estimates each stage's time to decide which valley town makes the best overnight stop.

How it's calculated

Naismith's Rule is a classic formula for estimating hiking duration.

The calculation runs in your browser - no data is sent to our servers. Map tiles come from OpenStreetMap (ODbL license), geocoding uses Nominatim (1 request/second limit), and elevation uses the Open-Elevation API backed by SRTM data. All are free, open services.

All calculations use the WGS84 datum (EPSG:4326), the same as GPS. For other datums (NAD27, NAD83, ETRS89), a separate conversion is needed. The difference is typically under 1 metre - negligible for most uses but important for survey-grade work.

The formulas match those in professional GIS software (QGIS, ArcGIS, Global Mapper), just in a browser-friendly form. For sub-metre accuracy, use professional software with ellipsoidal calculations. Results are shown in multiple units: km and miles for distance, km²/m²/hectares/acres for area, metres and feet for elevation. Conversion factors are exact (1 mile = 1.609344 km), so the only error source is input precision.

Related tools and resources

For more tools in this category, explore the related tools listed below. Each tool includes full documentation, examples and FAQs. Explore related tools in our Travel category for complementary functionality. See the Tools index for all 329 tools, or read our blog for in-depth articles on geography and maps.

Frequently asked questions

Does this account for rest breaks?

No - add 5-10 minutes per hour for breaks.

What is Naismith's Rule exactly?

It is a classic hillwalking rule of thumb: allow one hour for every 5 km of distance plus one hour for every 600 m of ascent. The calculator applies it to your route's numbers to produce a walking-time estimate. It was devised for typical Scottish hill conditions and assumes a reasonably fit walker with a light pack.

Does Naismith's Rule account for fitness?

No — it assumes one standard pace for a fit adult, so it is a baseline, not a personal prediction. Slower walkers, children, older hikers, and anyone with a heavy pack should add a generous margin, often 30–50% or more. Your own experience on known routes is the best calibrator: compare the estimate against your actual times.

Does it account for descents?

The classic rule counts only distance and ascent, not descent difficulty. Some walkers add 10 minutes per 300 m of steep descent, since knees and careful footwork slow you down. Technical or slippery descents can take far longer than the flat-distance math suggests.

How should I treat the result for safety planning?

Treat it as a planning estimate only — never as a safety guarantee. Weather, navigation errors, fatigue, and terrain can all stretch the real time well beyond the figure. Always carry a headlamp, extra food, and warm layers, and set a turnaround time based on daylight, not on the calculator's number.

Does terrain type affect the estimate?

Yes, and the rule does not capture it. Bog, boulder fields, scree, snow, and pathless ground all slow walking dramatically compared with a good trail. Add substantial margin for rough terrain, and consider local guidebook times which reflect the actual ground.

What about breaks and navigation stops?

Naismith's time is pure walking time with no stops included. Real days need food breaks, photo stops, map checks, and rest — typically adding 20–40% on a leisurely outing. Add your planned stops explicitly rather than hoping they fit inside the estimate.

Is there a version of the rule for very fit walkers?

Experienced fell runners and mountain athletes often beat Naismith's time comfortably, and some use faster variants like 6 km per hour on the flat. But the standard rule remains the safer planning baseline for groups. Plan to the slowest member, not the fastest.

Can I rely on this in bad weather?

No — wind, rain, snow, and poor visibility can double walking times or force a retreat, and no formula predicts that. In deteriorating conditions, your turnaround decision should come from the sky and the map, not from a time estimate. If in doubt, turn back early; the hill will still be there.

Data sources & methodology