Cross country ski app loops: what should be timed

Somewhere on your home trail there is a spot where your watch always beeps. Not the top of a climb, not the stadium, not anywhere you would ever choose to check your effort. Just a patch of snow, 1.00 kilometers of GPS track from the last patch of snow. That beep is the kilometer autolap, and it is the wrong tool for the sport you are doing.

The kilometer is a road unit

Kilometer splits come from road running, where they work beautifully. Roads are long, mostly flat lines. Effort is roughly constant, so equal distances are comparable, and a 4:52 followed by a 4:47 tells you something true.

A groomed ski trail is none of those things. It is a closed loop with a profile — climbs where a fast skier might triple their heart rate cost per meter, descents where nobody is working at all. Cut that loop into kilometer-sized pieces and each piece gets a different mix of up, down and flat. A climb-heavy split will always be slow. A descent-heavy split will always be fast. Neither number reflects how you skied; they reflect where the beep happened to land.

And the beep is not even reliable. On some Garmin devices, cross-country autolaps have arrived every 1.6 kilometers instead of every kilometer — a metric-to-imperial conversion problem that a Garmin representative on the company's own forum called a known bug. Skiers have also asked, for years, for ski-specific segments in Garmin Connect so that laps and climbs could be compared properly. The kilometer paradigm was inherited, not designed.

A loop is not a round number

Here is the deeper problem: your loop is not a round number, and it never will be. A real lit loop measures something like 3.63 km. The longer options at the same trailhead might be 5.42, 7.43 and 11.34. Groomers follow terrain, not arithmetic.

That means the kilometer grid and the loop grid drift past each other every lap. The 1 km beep lands somewhere new on the trail each time around, so you cannot even learn where the beeps are and read them cleverly. The one distance you repeat exactly — the full loop, stadium to stadium — is the one distance your watch never times on its own.

Three loops, one blur

It gets worse when you train the way most loop skiers actually train. A normal evening session might be the 3.63 twice to warm up, then two harder laps of the 5.42, then the 3.63 once more to cool down. Five laps, three of one loop and two of another, each one a self-contained piece of information.

In a kilometer-split file, that structure disappears entirely. You get one long activity with an average pace across warm-up, intervals and cool-down. The question you actually care about — was the second 5.42 faster than the first? — cannot be answered without scrubbing through a map replay and doing arithmetic on your phone in a cold parking lot.

Pressing the lap button manually solves this in theory. In practice it means remembering a glove-covered button press at the stadium every single lap, on the hardest days, in the dark. Miss one and the whole session's laps are off by one.

Timed by the trail, not by the grid

What should the unit be instead? The loop itself. Loop-based timing means the trail defines the split points: a lap starts and ends at the stadium because that is where the loop starts and ends, not because a counter rolled over.

Done properly, it looks like this:

• Every completed lap gets its own time, automatically — no button presses.
• Different loops in one session stay separate: three laps of the 3.63 and two of the 5.42 are five laps of two distances, not one blur.
• Lap times for the same loop line up across sessions, so 11:42, 11:31 and 11:18 form a history you can actually read.

Once laps are trail-defined, everything downstream improves. A personal best on the 5.42 means something, because every attempt covered exactly the same climbs in the same order. A fading last lap is visible the moment it happens. Your training log starts to speak the same language you use at the trailhead — laps of a named loop, not kilometers of nowhere in particular.

This is the problem Skibuddy was built around: it detects your loops, times every lap even when one session combines routes, and keeps the history straight — so the only beep you hear is one you would have chosen yourself.

The kilometer had a good run. On snow, count laps.