Phone-first GPS vs hardware satellite trackers

Why hardware satellite trackers won the first 17 years

Live race tracking as a public-facing audience experience started in earnest around 2009 with Tour Divide and the first wave of bikepacking ultras. The defining constraint of those races — riders going for days through wilderness with zero cell coverage — meant that the only viable technology was a satellite uplink. YB Tracking, Spot, and later Garmin inReach all converged on the same form factor: a small puck the rider clips to their jersey or bar bag, sending a position every 10 minutes over the Iridium or Globalstar satellite network.

Hardware satellite trackers solve coverage the right way for that use case. A rider on the Continental Divide can be 200 km from the nearest cell tower; the satellite link doesn't care. The hardware is rugged, weatherproof, and has multi-day battery life. The tracking is reliable in a way phone-based tracking couldn't be in 2010, when smartphones had patchy GPS chips, four-hour battery lives, and no offline-tolerant background-location APIs.

Those technical wins came with a structural cost: every rider needs a physical device. The organiser ships them out, the riders carry them, the organiser collects them after. The unit economics are punishing.

The economics of hardware tracking

A typical hardware-tracker line item for a 150-rider race breaks down something like:

• Tracker rental or device cost: £100–£300 per unit
• Satellite messaging plan: £20–£80 per device for the duration of the event
• Outbound shipping (to riders, often international): £15–£40 per device
• Return shipping (riders post the trackers back): £15–£40 per device
• Loss + damage budget (5–15% never come back): cost of replacement
• Customer support time spent chasing missing devices: large and uncounted

For a marquee 250-rider ultra, the all-in tracking cost from a hardware vendor lands in the £20,000–£50,000 range. That math works when the event itself is generating £100k+ of entry revenue and live tracking is mission-critical to the brand. It doesn't work for a 60-rider regional gravel race with a £40 entry fee.

This is the structural reason 95% of bike races have never had live tracking. It isn't audience — the audience for a regional race is just as keen to watch as the audience for Tour Divide. It's that £50 per rider in tracking costs eats the entire entry-fee margin.

What phone-first GPS tracking does differently

Phone-first platforms replace the dedicated hardware with the smartphone every rider already has. The same GPS chip, the same offline-tolerant background-location API, the same satellite positioning — just inside a device that costs the organiser zero to deploy and zero to recover.

What changed between 2010 and 2026 that made this viable:

• Smartphone GPS chips became as accurate as dedicated trackers (often more accurate, since they fuse GPS + GLONASS + Galileo + BeiDou constellations).
• Background-location APIs on iOS and Android became reliable — Apple's CoreLocation and Android's FusedLocationProvider give native apps disciplined, battery-efficient background tracking for hours at a time.
• Phone battery life caught up; a modern rider phone with airplane mode + cellular-data-only + dimmed screen will hold tracking for 12+ hours on a single charge, and battery packs handle anything longer.
• Cellular coverage in the European gravel + road racing terrain expanded enough that the average race route now has 80–95% coverage. The remaining gaps are handled by on-device queueing.
• Native offline-queue libraries (Aster runs on Transistor BackgroundGeolocation) survive app kills, phone restarts, and OEM-aggressive background-process killing.

The result: phone-first tracking is now reliable enough for serious racing, while keeping the marginal cost per rider effectively zero.

Where each one is still the right choice

Hardware satellite trackers are still right when:

• The race goes through long stretches with literally no cellular coverage — the Continental Divide, the Iditarod Trail Invitational, the Atlas Mountain Race deep desert sections.
• Riders are expected to be off-grid for 12+ hours in a single push, longer than a phone battery + power bank can comfortably cover.
• The audience expectation for the marquee event is hardware-grade reliability (a single missed ping makes the front page of CyclingTips).
• The race already has the operational infrastructure for tracker shipping + recovery, and the entry-fee economics support a £100+ per-rider tracking budget.

Phone-first is the right choice when:

• The route has reasonable cellular coverage (most road, gravel, and XC mountain bike racing in Europe and North America).
• The race is anything other than a multi-day ultra — daily-format events, stage races, time trials, group rides, fondos, regional and club racing.
• The organiser is allergic to the per-rider hardware cost or doesn't have the logistics capacity for tracker shipping and recovery.
• The audience experience matters as much as the raw tracking — the watcher map, leaderboard, gaps, ETAs, SOS visibility are all richer on a platform built native for phones.

The honest hybrid case

A serious bikepacking ultra in 2026 should probably run both. Hardware trackers for the leaders and any rider explicitly going through known dead zones for hours at a time; phone tracking for everyone else and as a backup layer for the lead group. Both surfaces feed the same watcher map, and the rider's profile shows whichever ping was most recent.

For everything outside the marquee ultras — the regional race, the club championship, the Tuesday-night chaingang, the 95% of the market that has never had tracking — phone-first is the only economics that makes the format viable at all.