Trailhead Lab All tools
Hiking & Trails

Hiking Pace Estimator

Tobler hiking function with grade, pack weight, surface, and party-size corrections.

Inputs

Result

Enter values above and the calculator will appear here.
Advertisement

A natural placement between the calculator and the explanation.

What this solves — and what it doesn't

This calculator uses Tobler’s hiking function (1993), which models walking speed as a function of slope: a fit walker moves fastest on a slight downhill (~ -3% grade) and slowest on steep uphills. We then apply a surface multiplier, a pack-weight penalty (about 1.5% slower per kg above 5 kg), and a standard ascent allowance (1 hour per 600 m of climb).

Unlike the original Naismith rule (5 km/h flat + 1 h/600 m up), this approach responds to grade directly, so a rolling 10 km at 6% feels different from a 10 km walk on a flat rail-trail.

How to read the result

The output is total elapsed time, not moving time. We add your rest input on top of the moving estimate. If you don’t know how long you’ll rest, a fair default for a 10 km day is 15 to 30 min broken into 2 to 3 snacks and a long lunch.

The pace assumption is for an adult moving solo on a marked trail. Children, dogs, large groups, or technical descents will move slower. Add buffer when in doubt.

Limitations

Frequently asked questions

Why is my time longer than what AllTrails says?

AllTrails’ times come from a generic Naismith-derived model with no surface or pack adjustment. Our model is more conservative on rougher ground and heavier loads.

What if my route has lots of ups AND downs?

Enter the net gain. Tobler handles descents as part of the slope average; very up-and-down routes feel slower than they read, so add a 15 to 20% buffer mentally.

Does party size matter?

Larger parties move slower because the slowest member sets the pace. Multiply our output by 1.1 for groups of 4 to 6, 1.2 for 7+.

How do I use Hiking Pace Estimator step by step without mistakes?Follow the order given in the usage section: Tobler hiking function with grade, pack weight, surface, and party-size corrections. The step-by-step part matters less than the unit check that sits inside it. Confirm every unit matches the thing you are actually trying to measure before you press calculate - that single check catches more wrong answers than any other habit, and it costs about ten seconds.
What are the common mistakes when using Hiking Pace Estimator?Most common mistakes come down to four habits: entering 20 when the field expects 0.2 because the field is a percentage; leaving a field blank and accepting the default without checking what it stands for; changing one input and reading a result that was calculated before the change; and quoting the output as an exact figure when the page describes it as a reference estimate. Press calculate again after any edit, and treat the number as a reference point rather than a final answer.

Related tools