Routster

Charts and terrain

What the panels under the map are actually measuring.

Mistake detection

Analyse looks for three kinds of event in the track itself, independently of any split times:

TypeTriggerReported as
StopPace slower than about 12 min/km for at least 5 seconds, with under 5 m of progressSeconds lost
SlowdownLocal pace at least 1.5× your own rolling median for the runSeconds lost
BacktrackA heading reversal of 120° or more inside a 10-second windowThe turn angle, or seconds lost where that can be estimated

The thresholds are relative to your own pace rather than an absolute standard, so a slower runner is not flagged for being slow.

What is suppressed

Three situations produce a candidate that is not a mistake, and each is filtered out:

  • Path following. A slowdown on a path is usually the path bending rather than hesitation.
  • Contour dodging. A route that traverses rather than climbing straight reads as a deviation but is a route choice.
  • Punch and turn. A sharp reversal within about 25 m of a control is the runner leaving towards the next one, not a backtrack.

Sprint events use tighter corner tolerances than forest ones: a 120° turn round a building is a street corner rather than a navigation error.

Where the headline number comes from

Where the event has split times, the mistake count and time lost in the headline are taken from the splits, measured against the field on the same course on the same day. The GPS detector above is the fallback for a run with no splits, so the number can change when the organiser uploads the results file.

Terrain

Analyse classifies the ground under each point of your track from the map's own colours into eight classes: path, open, runnable forest, slow forest, fight, marsh or water, rock, and unknown. From that it computes, per terrain and per leg, how far you ran in it, what share of the leg it was, your raw pace and your terrain-adjusted pace.

Raw pace counts a route through green as slow; adjusted pace measures how well that green was run.

Warm-up and cool-down terrain sit in their own card, folded by default, so the race figures exclude the jog to the start.

Pace, elevation and heart rate

Plotted against cumulative distance, with elevation filled to show the profile. Hovering moves a marker along the track on the map, so a spike in the chart can be located on the ground.

Heart rate appears where the file carries it, plotted against your stored zone scale rather than the run's own minimum and maximum, so two runs are comparable. Set your zones in Settings before reading the colours.

The deviation chart

Available once you have sketched a route. It plots the perpendicular distance between your GPS position and your drawn line, with a reference at 30 metres and every span above it listed with a jump control.

Off-route spans are reported here and are not counted as mistakes — see Route guess.

Charts are always on white

Every chart plots on a white background in both light and dark themes, and takes its axis, grid and text colours from a fixed palette rather than from the theme, so pace and heart-rate colours mean the same thing in both.

Reordering the panels

Mistakes, legs, terrain, charts and deviation can be reordered, hidden or set to start collapsed. A hidden section is not rendered or computed.