ForHosting KIT · Health & fitness

Hiking calculator

A 10 km trail with 600 m of climbing takes 3 hours of book time and burns about 1719.9 kcal at 70 kg: Naismith's rule for the clock, and a grade-based effort level for the energy. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Distance
10
Elevation
600
Weight
70
You get
Duration hours
3 kcal
Duration minutes
180
Hours
3
Minutes
0

A hiking calculator turns three numbers you already have from a map and a bathroom scale into estimated trail time and energy cost: trail distance in kilometres, cumulative elevation gain in metres, and body weight in kilograms. Book time follows Naismith's rule, which allows one hour for every five kilometres of travel plus one hour for every six hundred metres of ascent, the same book-time identity used by alpine clubs and guidebook writers. Average grade, which is gain divided by horizontal distance, then selects a hiking metabolic equivalent so a steep climb is not billed like a flat path. Kilocalories follow the ACSM oxygen-cost identity that multiplies MET, body mass, and minutes.

What hiking time and calories mean and how Naismith sets book time

Hiking duration is not the same as walking time on a city sidewalk. A trail that is eight kilometres on the map can take twice as long as a flat pavement walk once you add a few hundred metres of climbing, rest steps on loose scree, and the slower cadence of a loaded pack.

Naismith's rule, published in 1892 by the Scottish mountaineer William Naismith and still the default book time in British and alpine guidebooks, encodes that extra cost as two additive terms: one hour for every five kilometres of horizontal travel, plus one hour for every six hundred metres of ascent. This calculator implements that identity exactly. Calories burned on the same hike are a separate estimate of extra energy, not a laboratory calorimetry measurement and not a full daily energy expenditure figure.

Exercise physiologists express that cost through metabolic equivalents. One MET is the oxygen cost of quiet sitting, about 3.5 millilitres of oxygen per kilogram of body mass per minute. Cross-country hiking sits near six METs in the Compendium of Physical Activities; climbing hills raises the band.

This calculator interpolates MET as six plus three-tenths times average grade in percent, then clamps the result between five and twelve so a vertical scramble or a dead-flat towpath cannot invent an unbounded cost. Kilocalories follow the ACSM oxygen identity: MET times 3.5 times body weight in kilograms times duration in minutes, divided by two hundred. Treat the figures as transparent planning numbers you can recompute by hand, not as medical advice or a promise of a summit time, which also depends on fitness, weather, pack mass, and trail surface.

Practical tips, limits, and related searches

Measure distance on the trail line, not as a straight crow-flies span between car park and summit, and prefer cumulative ascent from an elevation profile rather than the difference of two spot heights, which hides the ups and downs of a rolling ridge. Stay inside the published limits: distance from a thousandth of a kilometre up to five hundred kilometres, elevation gain from zero to twenty thousand metres, body mass from one to five hundred kilograms. Extreme grades clamp MET at five or twelve rather than extrapolating without bound.

Naismith does not add time for descent, so a hike that is all downhill after a lift still reports book time from the horizontal term only; if your group is slower than five kilometres per hour on the flat, treat the result as a lower bound and add your own rest and navigation margin.

This page targets people searching for a hiking time calculator, a hiking calorie calculator, or estimated hours and kilocalories from trail distance and elevation gain; it is not a running, cycling, swimming, or city-walking estimator, not a heart-rate calorie model, and not a TDEE planner. Prefer this capability when you already know kilometres, metres of gain, and kilograms and only need a deterministic book time and energy figure.

Round-trip checks are easy: ten kilometres with six hundred metres of gain at seventy kilograms should return three hours and about 1719.9 kilocalories, and a five-kilometre flat walk at the same mass should return one hour at MET six.

Day-hike planning and guidebook book time

Walkers enter mapped kilometres, cumulative metres of gain, and body weight to fill an honest hours-and-kcal column before choosing a start time or a turnaround.

Coaching and training-load logs

Coaches store the same three numbers after a hill session so weekly load tables stay on one Naismith-plus-ACSM identity instead of mixed rules of thumb.

Backpacking calorie and itinerary sheets

Multi-day planners convert each stage's distance and ascent into book time and kilocalories so food drops and daylight windows are sized from the same contract.

How is hiking time calculated?

Book time follows Naismith's rule: hours equal distance in kilometres divided by five, plus elevation gain in metres divided by six hundred. That is one hour per five kilometres plus one hour per six hundred metres of ascent.

How are hiking calories calculated?

Average grade percent is one hundred times elevation in metres divided by distance in metres. MET equals clamp(6 + 0.3 × grade%, 5, 12), then kilocalories equal MET × 3.5 × body weight in kg × duration in minutes / 200 (ACSM oxygen-cost identity).

What happens if distance is zero, negative, or missing?

Distance must be a positive finite number greater than zero. A zero-length or negative trail is rejected rather than treated as a completed hike.

Can elevation gain be zero?

Yes. Zero metres of gain is a flat trail: book time is then only the horizontal Naismith term (distance / 5 hours) and MET stays at the six-MET hiking floor before grade is added.

Is the hiking calculator free?

The browser tool is free and runs locally.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/sports/hiking

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/sports/hiking \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"distance":10,"elevation":600,"weight":70}'
{
  "distance": 10,
  "elevation": 600,
  "weight": 70
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "sports.hiking",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

max_distance_km500
max_elevation_m20000
max_weight_kg500
min_distance_km0.001
min_weight_kg1
HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Distance that is not a positive finite number fails with invalid_input so a zero-length or negative trail never looks like a completed hike.

What hiking time and calories mean and how Naismith sets book time

The estimate is deterministic: identical distance, gain, and weight always yield the same rounded JSON, with no network, no random seeds, and no wall-clock dependence.

How to call the API and what comes back

Zero is a legitimate flat trail; negatives fail because this contract models gain, not net change including descents. A classic check is ten kilometres, six hundred metres of gain, and seventy kilograms: book time three hours, grade six percent, MET 7.8, about 1719.9 kilocalories. If you already know a walking pace and only need distance over speed, that is a different search; this landing is specifically hiking duration and calories from distance, elevation gain, and body weight. Send a JSON body with three required fields. The field distance is trail length in kilometres, a finite positive number between 0.001 and 500, with aliases distance_km, km, trail_distance, and d. Zero, negatives, empty strings, and non-numeric values fail with invalid_input and are never charged; the product contract is that distance that is not positive is rejected rather than rounded or treated as a flat zero-hour hike. The field elevation is cumulative elevation gain in metres, a finite number between zero and twenty thousand, with aliases elevation_gain, elevation_m, gain, ascent, and ascent_m. The field weight is body mass in kilograms, a finite positive number between one and five hundred, with aliases body_weight, weight_kg, kg, and mass. On success the response echoes cleaned distance_km, elevation_m, and weight_kg; publishes grade_percent, the interpolated met, and pace_kmh as distance over Naismith hours; returns duration_hours, duration_minutes, hours, minutes, and a short time_label; returns calories_kcal and calories_burned as the same total with unit set to kcal, plus kcal_per_hour and kcal_per_km; and includes formula, method naismith_met_acsm, a short message, and an ordered steps array showing the Naismith substitution, grade, MET clamp, and ACSM identity. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.

Practical tips, limits, and related searches

Use a recent weigh-in in kilograms; this contract takes kilograms so API clients do not need a separate unit library. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send a zero distance to test client validation. API pricing remains $0.002 per successful request with unit item.

Read the full KIT documentation →