Walking Time Calculator

Calculate how long it will take to walk between two places based on distance and pace.

Route Details

How the Walking Time Calculator Works

Enter a starting address and a destination, and the calculator runs both through OpenStreetMap's geocoder (Nominatim) to find their coordinates, then asks the OSRM foot-routing engine to find the shortest walking route between them along actual paths and pavements. You get the distance in metres or kilometres, an estimated walking time, and a map showing the route in blue.

Pick a walking pace before you calculate. Slow (3 mph / 4.8 km/h) is comfortable strolling. Normal (3.5 mph / 5.6 km/h) is the OS Naismith's-Rule baseline used by most fitness trackers. Brisk (4 mph / 6.4 km/h) is purposeful walking with a destination in mind. Fast (4.5 mph / 7.2 km/h) is speed walking, the upper end of what most people sustain over distance. Each step up the pace knocks 10-15% off the time.

Why Walking Times Vary So Much

The 'normal' 5 km/h figure is an average for a fit adult on flat, uncrowded ground with no breaks. Real walks deviate. Hills slow you down (Naismith's Rule adds about a minute per 10 m of ascent on top of the flat-ground time). Crowded city pavements break your stride. Carrying shopping, pushing a buggy, or walking with a dog all lower pace. The route engine returns the shortest path geometrically, but the time estimate assumes you walk it without stopping.

For routes you do regularly (the school run, walk to the station, dog loop in the park) you'll quickly learn whether you fall above or below the calculator's prediction. Most people overestimate their walking pace by 10-20%, then under-allocate time and arrive flustered. A useful rule of thumb: if you really need to be somewhere at a specific minute, add 10% to the calculator's estimate.

Walking Times for Common Distances

DistanceSlow (3 mph)Normal (3.5 mph)Brisk (4 mph)
500 m6 min5 min4 min
1 km12 min11 min9 min
2 km25 min21 min19 min
3 km37 min32 min28 min
5 km (3.1 miles)62 min53 min47 min
8 km (5 miles)100 min85 min75 min
10 km (6.2 miles)124 min107 min93 min

Useful Cases Beyond 'How Long Will It Take?'

Comparing two routes when one looks shorter on the map but goes uphill or through busy areas. Working out whether walking to the next station saves enough on a fare to be worth it. Checking whether a hotel really is '5 minutes from the venue' as advertised (often it isn't). Time-boxing dog walks, school runs, or the nip-to-the-shop journey when you're trying to fit one into a tight slot.

Walking distance also affects the property market: 'within 10 minutes' walk of a station is a real premium in commuter areas, with research from estate-agent indices regularly putting that at a 5-10% price uplift. For longer-form planning the [Distance Calculator](/distance-calculator) gives you straight-line distances between cities, useful when walking isn't really an option but you want to feel the scale of the journey.

Frequently Asked Questions

Does the calculator account for hills?

No, not directly. The OSRM foot-routing engine returns flat distance and applies a level-ground pace. If your route has serious hills, add about 1 minute per 10 metres of ascent (Naismith's Rule). For most urban walks the elevation change is small enough not to matter; rural and coastal walks can be quite different.

What walking pace should I assume for a child or older adult?

Children under 8 typically walk at around 2-2.5 mph (3.2-4 km/h). Older adults vary widely: a healthy 70-year-old often holds 3 mph; a less mobile walker might be at 1.5-2 mph. Pick 'slow' or even slower than the slow setting and add a margin. The calculator's pace presets target adults of average fitness.

Why does the route follow a strange path?

The OSRM foot-router follows real OpenStreetMap data on pedestrian paths and rights of way. Sometimes 'the obvious shortcut' isn't actually a public footpath and the router avoids it correctly. Sometimes a path is missing from OSM entirely and the router takes a longer detour. If the route looks wrong, check whether all the relevant footpaths are mapped.

Can I use this for non-UK addresses?

Geocoding is biased to UK addresses (the search adds 'UK' to the query). The OSRM router itself works globally, so non-UK routes do compute, but the address lookup may match the wrong country if you enter a place name shared between the UK and elsewhere. Use full city, country names for non-UK searches.

How does this differ from Google Maps walking directions?

The underlying maths and pace assumptions are similar (Google also uses around 5 km/h for walking), but the data sources differ. Google uses its own road and footpath data, while this tool uses OpenStreetMap. For most UK routes the answers agree to within a couple of minutes; for poorly-mapped paths or recently-built developments, one source may have data the other doesn't.

More tools β†’