Routster Analyse
Upload the GPS track from a race and find out where the time actually went.
Analyse takes three things — an orienteering map, a course, and your GPS track — and puts them in the same coordinate system. Everything else follows from that: which leg you were on at any moment, how far your line deviated from the straight one, where you slowed down and for how long, what the terrain under you was, and how all of it compares to everyone else in your class.
Uploading an event
The organiser's job, and the two timing rules that make everybody else's analysis work.
Layers, tiles and presentation maps
Multi-loop trainings, scanned sheets, and maps with the course already printed on them.
The AI coach
What it reads, what the tiers change, and how to get a better review out of it.
Settings reference
Every default you can set, and the handful that genuinely change the experience.
Every analysis belongs to an event
An analysis is created in one way: an event exists, and you add your run to it. There is no standalone upload.
A training run is an event with its competition level set to training, which you can create yourself in a couple of minutes.
Most of what an analysis reports is comparative: time lost on a leg is measured against the rest of the field on the same course on the same day. The event is what supplies that field.
What goes in
| Input | Who provides it | What it unlocks |
|---|---|---|
| The map, georeferenced | The organiser, in the event wizard | Everything. Without a pixel-to-world transform nothing can be aligned. |
| The courses and classes | The organiser, from an OCAD, Purple Pen or IOF course file | Leg splitting, control rings, per-leg statistics, the route sketch step |
| Your GPS track | You — a GPX file, Strava, or a connected watch service | The run itself: pace, deviation, mistakes, terrain |
| Split times for the whole class | The organiser, as an IOF XML result list or a WinSplits link | Field comparison, honest time-lost figures, and the AI coach's field tools |
What an analysis without split times still does
Adding your run
Three sources, and the choice has consequences beyond convenience:
| Source | How | Privacy consequence |
|---|---|---|
| GPX file | Export from your watch software and drop it in | You choose any privacy tier |
| Strava | Connect once, then pick the activity | Forced to fully private — Strava's API terms do not let us show their data to anyone but you |
| Connected watch service | Polar Flow or Suunto, via Open Wearables | You choose any privacy tier |
For a track other runners can use, export it from the watch or import it through a watch connector rather than Strava. See Run privacy.
After the upload you can sketch the route you remember running, before seeing the GPS. The step is skipped by default — see Route guess.
What comes out
- Three views of the map. Full course for the shape of the race, per-leg for one decision at a time, and live playback for the race replayed with the field alongside you.
- Detected mistakes — stops, slowdowns, off-route excursions and backtracks, each with an estimated cost and a position on the map.
- Field comparison from the split times: leg ranks, place progression, time lost measured against your own level rather than against the winner, and a dozen more views. See Split times.
- Terrain and charts — pace by terrain type, heart rate, elevation, and deviation from the straight line. See Charts and terrain.
- An AI review that reads all of the above through a set of numeric tools and writes it up leg by leg. See The AI coach.
Sprint gets extra machinery
A sprint event runs an extra pass: the map is turned into a passability model and the shortest legal path for each leg is computed on it. That produces an optimal line to compare against, a ghost runner that follows it, and GPS snapping for noisy urban tracks. See Sprint analysis.