Live tracking for a relay race where the tracker passes between runners

If you mean one live GPS tracker that’s physically passed from runner to runner, that’s a common relay setup. Relay Iowa, for example, gives each team a GPS device to wear and pass like a baton; friends and family can follow its location live. Coverage gaps can interrupt updates. (relayia.org)

If you’re looking for an app, RaceJoy supports relay-team GPS tracking using runners’ phones, while TeamSplits focuses on shared progress and one-tap handoffs. (racejoy.net)

Are you trying to track a particular race, or find a setup for your own relay?

The core problem is that a baton-style tracker separates the device from the person. The map shows where the device is, but the runner it belongs to changes at every exchange, and the device spends time in a van between legs. Here are the common ways organizers handle it:

1. One tracker per team, passed like a baton. Relay Iowa does this: it will be passed from runner to runner like a "baton." The runner currently on the course should always wear the GPS. This is cheap, but the handoff becomes a point of failure. If nobody updates the record at the exchange, the map shows the wrong runner.

2. Separate trackers for runners and the van. The Chronorace-based tracker project shows this approach. Each runner has a tag for the team, and one in the vehicle your runner travels in between legs, such as VAN1. The display then shows whether someone is running, riding in the van, or resting. This avoids handoffs, but it needs more hardware and the status logic is more involved.

3. Phones with leg start and stop. RaceJoy's relay mode has each runner click the Start My Leg button to start their personal clock for their leg. RaceJoy auto detects when they complete their leg. Team members can also see one another's positions live. This works well if runners carry their phones, and it can be adjusted on race day.

4. Chip timing at exchanges as anchor points. Timing chips can supply exact checkpoint reads. RaceResult's Track Box, for example, uses mobile connectivity to transmit all transponder detections, along with their GPS position, to any preconfigured server endpoint. The SingleTrackEvents project uses chip reads as a second source alongside GPS, and it lets whichever is newer place the runner.

Practical design for a DIY setup:

• Model identity separately from the device. Store a "device X is with runner Y from time T" record, and make the handoff a logged event, either a button press at the exchange or a scan.
• Plan for dead zones. Relay Iowa notes that the live tracking will directly reflect that poor cell coverage. Choose a tracker that stores data and uploads later, or label the position as stale. The SingleTrackEvents project estimates position from the runner's pace once a fix is older than three minutes, and marks it as an estimate.
• Use the van tracker when the device is in transit. If the device rides in a vehicle between legs, the display should show "in van" rather than a fake position on the course.
• Get consent before publishing. The Chronorace-based project warns that this page shows a real person's live location to anyone with the link. Keep the page out of search indexes unless the runners want otherwise.

Commercial options: RaceJoy, Webscorer, and RTRT.me use runners' phones, and RaceMap and Track Box-style systems use dedicated trackers. Those are better choices than building your own if you don't need custom logic. Ask the provider directly whether it supports relay handoffs and how it handles a tracker that is passed to the next runner.

If you tell me the event size, budget, whether runners carry phones, and whether you're building it yourself, I can recommend a specific setup.

For relay races where a tracker must be passed between runners, the most effective solution is a single, dedicated GPS relay baton or a ruggedized tracker unit that travels with the team.

Unlike individual tracking—where every participant carries their own device—this approach treats the baton as the "source of truth" for the team's location.

How Baton-Based Tracking Works

1. Dedicated Hardware: Race organizers typically use custom-built or specialized GPS trackers housed in a casing that mimics a relay baton. These devices are designed to be durable, weather-resistant, and ergonomic for runners to carry.
2. Continuous Tracking: Because the tracker is handed off at each transition point, the live map on the race's tracking platform shows a single, continuous line for the team. This eliminates the need for spectators to switch between different runners' profiles.
3. Autonomous Operation: Modern relay trackers are often "set and forget." Once active, they transmit GPS coordinates via cellular or satellite networks to a central server at set intervals (e.g., every 15–30 seconds), allowing for real-time visualization on a public race map.
4. Logistics: Many organizers prefer owning a "fleet" of these baton trackers. This avoids the logistical burden of renting equipment for every event and ensures that the devices are branded and pre-configured for the specific race format.

Alternative Approaches

If a custom baton tracker is not feasible for your event, other common methods include:

• Smartphone Apps: If the race is less formal, teams can use dedicated race-tracking apps (like RaceJoy or similar platforms). The "baton" becomes a shared team account or a designated runner's phone, though this requires coordination during handoffs to ensure the tracking session is active for the correct person.
• Chip/Transponder Timing: For high-precision events, organizers use passive or active transponders (worn by each runner or attached to the baton) that trigger timing mats at transition points. While this provides accurate split times, it does not offer the same "moving dot" live map experience as GPS trackers unless combined with secondary technology.

Key Considerations for Organizers

• Battery Life: Since the tracker will be in continuous use for the duration of the relay (which could last 24+ hours), ensure the hardware has sufficient battery life to last the entire event without recharging.
• Signal Reliability: In remote trail or mountain relays, standard cellular-based GPS may lose signal. Some high-end trackers use satellite connectivity to ensure coverage even in deep wilderness.
• Handoff Protocol: Regardless of the technology, clear communication with teams is essential. Runners must know to physically transfer the device and ensure the next person has it securely before the previous runner stops their own personal tracking (if applicable).

Yes—live tracking can work with one GPS tracker handed from runner to runner. The main requirement is that the tracking service supports a team or relay tracker: it follows the device’s location, while your team records the handoff so viewers know who currently has it.

A few options to investigate:

• RunnerBeam advertises a dedicated relay-baton product and live race maps. ¹
• Racemap offers live maps using GPS devices or an app, and describes event tracking for relays. Ask whether its setup can keep one tracker assigned to a team as runners change. ¹⁴¹⁵
• Owaka Live provides event GPS trackers and a public live map; confirm its tracker assignment and handoff workflow with the provider. ¹²

Before choosing, check the details that matter for your race: battery life for the full event, mobile coverage along the course, how quickly positions update, whether the tracker can stay paired to the team rather than an individual, and how handoffs are marked. Test the entire route if possible—GPS location alone doesn’t guarantee that the position will reliably reach the public map.

If you share the race length, location, number of teams, and whether you’re organizing it or running as a team, I can narrow down the best fit.