Live tracking for bikepacking + ultra-distance races

Why ultras built dot-watching

Live race tracking as a public-audience product didn't start with road racing or mountain biking — it started with ultra-distance bikepacking. Tour Divide (4,400 km Banff to Mexico, racing the Continental Divide route) put trackers on its first field around 2009. Trans Am (6,800 km Astoria to Yorktown) followed. By 2015 the marquee bikepacking calendar — Atlas Mountain Race, Silk Road Mountain Race, Indian Pacific Wheel Race, Iditarod Trail Invitational — had standardised on live tracking as a defining feature.

Ultras built the audience because the format invited it. A road race finishes in five hours; the live audience window is short and most spectators want to be there in person anyway. An ultra finishes in two to four weeks; the audience window is long, the riders are spread across continents, and almost none of the audience can be there physically. The watch page IS the race for everyone except the riders themselves.

Dot watching as a verb predates phone-first tracking — it came out of a watch-page-on-a-laptop era when the dot literally was the entire ride from the audience's point of view. The visceral simplicity of a dot moving across a continent over weeks is what made it a category.

What's different about an ultra rider

An ultra rider's tracking constraints are unlike any other cycling discipline:

• The rider may be in true wilderness for days at a time — the Continental Divide, the Atlas Mountain interior, the Iditarod Trail in winter. Cellular coverage is patchy at best and absent for stretches measured in days, not hours.
• Battery life and charging strategy is a core part of race planning. The rider's phone is one of multiple battery-dependent devices (head unit, lights, dynamo cache) sharing a fixed daily charge budget from a hub dynamo or solar panel.
• The tracker is left on continuously for weeks. A 15-hour daily race-day is a short ride; sleep is taken at the side of the road and the tracker keeps running.
• The audience appetite for granularity is extreme. Watchers refresh every few minutes for weeks. A single missed ping triggers "is X OK?" forum threads.

Hardware satellite trackers (Spot Gen 4, Garmin inReach Mini 2, Zoleo) became the default for these races for a reason — they solve the wilderness-coverage and battery-life problems in ways no phone-based solution could in 2010 or 2015.

Where phone-first tracking is now viable for ultras

Phone-based tracking has caught up enough that the ultra-tracking question isn't "phone OR satellite" anymore — it's "which combination, for which event":

• Phone-first works for ultras held in regions with 80%+ cellular coverage on the route — most European bikepacking, most US east-coast and west-coast routes outside true wilderness, Australia's coastal stretches.
• Phone-first as the primary tracker, with the rider carrying a satellite messenger as a private SOS device for the gaps, is a viable cost-reduction for ultras with mixed-coverage routes.
• Pure satellite is still the right call for the marquee wilderness ultras — Tour Divide, Iditarod, Atlas Mountain Race deep desert stages — where multi-day gaps between cell coverage are the norm.

On Aster specifically, the offline-tolerance is the feature that makes ultras viable: the phone's GPS chip records every position to an on-device SQLite queue for up to seven days; the queue drains the moment cell signal returns and backfills the polyline. A rider going through a 48-hour dead-zone re-appears on the map with the full ride visible, not just the moment they re-emerged.

What the ultra audience actually watches

The watch experience an ultra audience wants is different from the road-race audience. A road-race watcher wants the leaderboard and the live map for five hours and then they're done. An ultra watcher comes back daily for three weeks. What sustains them is different:

• Daily mileage and elevation, rider-by-rider, so the audience can see who pushed hard yesterday and who took an unscheduled rest.
• Stoppage time visibility — how long each rider has been at their current location, so the audience can read "sleeping" vs "mechanical" vs "hold-up".
• Cumulative ETA to the next checkpoint or the finish, recalculated as the rider's pace changes through the race.
• Rider-side commentary — short voice notes or text dispatches from the riders themselves at re-supply stops, surfaced into the watcher feed.
• Editorial layer — DotWatcher-style daily race reports synthesised from the rider movement plus the rider commentary plus social media. Most ultras outsource this today; the platform that builds it in-house wins the audience attention.

What this means for an ultra organiser deciding

If you're organising a bikepacking ultra and deciding on a tracking approach for 2026 or 2027, the right framing is:

1. Audit your route for cellular coverage. Pre-ride with a phone and a coverage-mapping app, or pull network-provider heat-maps. Calculate the longest single dead-zone gap.
2. If the longest gap is under 12 hours and you have realistic 80%+ coverage along the route, phone-first tracking handles the job — the queueing fills the gaps and the per-rider cost drops to zero.
3. If the longest gap is 24-48 hours but most of the route has coverage, run phone-first as the public-audience tracker and let riders carry a satellite messenger as their private SOS device. Total per-rider hardware cost stays under £100.
4. If the route includes multi-day wilderness sections (Tour Divide, Iditarod, deep desert ultras), satellite remains the right primary surface and phone tracking is a complementary layer in the covered sections.

Aster handles the first two cases natively. For the third — the marquee wilderness ultras — the right platform is still a hardware-based tracker; Aster could play a complementary role on the covered sections of the same race but isn't the primary tool there yet.