Hiking time plan by legs

Turn the legs of a tour into a time plan. The server calculates the walking time per leg with the DIN 33466 rule, adds breaks and shows arrival and the latest time at each point.

Input

Result

A table of legs with distance, ascent, descent, walking time, break, arrival and latest time, the sums, the planned end, the rule and a short plan text.

A tour plan needs times that a group can follow. This tool calculates the walking time of each leg with the rule of DIN 33466: 4 km per hour on the flat, 300 m per hour up and 500 m per hour down, the larger value plus half of the smaller. It applies a group factor, adds breaks and shows the arrival at each point. With a latest return it also shows the latest time at each point. Weather, terrain and the group stay with the guide.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Hiking guides, mountain leaders, clubs and teachers who plan day tours.

Typical uses

Plan the times of a day tour.
Set a latest time for the summit.
Compare a fast and a slow group.

Example

Input

Tour: Three-peak round from Mill Valley Guide: T. Berg Date: 21 June 2026 Legs: id,leg,distance_km,ascent_m,descent_m,break_min T1,Car park to Alder hut,4.5,600,0,20 T2,Alder hut to summit,2.2,450,50,30 T3,Summit to the valley,7.8,0,1000,0 Start time: 08:00 Latest return: 17:00 Group factor: 100 % (rule as it is) Notes: Meeting point at the car park. Packed lunch for the summit.

Result

A table of legs with distance, ascent, descent, walking time, break, arrival and latest time, the sums, the planned end, the rule and a short plan text.

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price: usually 1–3 credits
Available with: Free, With package
Input limit: One page with up to 12,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: hiking_time_plan. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "hiking_time_plan", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Who does the calculation?

The server calculates all sums from the table. The AI only writes the text and cannot change the figures.

Which rule is used?

The rule of DIN 33466: 4 km per hour, 300 m per hour up, 500 m per hour down; the larger value plus half of the smaller, times the group factor.

Does the plan say the tour is safe?

No. It only calculates times. Weather, terrain, daylight and the group are judged by the guide on site, and sentences on safety are removed by the server.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.