Track3D Guide
Using a SPOT Satellite Tracker for Ultramarathon Race Tracking
A SPOT satellite tracker can keep sending a runner’s location when mobile reception disappears. For an ultramarathon crew, that solves the first problem: knowing where the runner is. Track3D adds the race context around those satellite points, matching them to the actual course so the crew can see race progress, the next checkpoint, Adaptive ETA, Finish ETA and cutoff context.
Can a SPOT satellite tracker be used for ultramarathon race tracking?
Yes. A SPOT device can provide satellite location updates beyond normal mobile coverage, and Track3D Crew can use a configured SPOT XML Feed as a race tracking source.
If all you want is a dedicated satellite tracking source, you do not necessarily need every communication feature offered by a more complex satellite messenger. Track3D takes the location evidence SPOT provides and turns it into information a crew can act on: where the runner is on the course, which checkpoint comes next and when they are likely to arrive.
Can a SPOT satellite tracker track an ultramarathon runner?
Yes. SPOT tracking devices are designed to send GPS locations through the satellite network when the runner is beyond reliable mobile coverage. Those transmitted locations can be shared through SPOT Mapping and, when an XML Feed is configured, made available for services such as Track3D.
SPOT Gen4 is a good example. Its normal tracking service supports 5, 10, 30 and 60 minute intervals, with 10 minutes as the default. SPOT also offers a 2.5 minute interval through its Extreme Tracking service. The exact options depend on the device and service attached to the account.
That makes SPOT useful for trail and ultramarathon races where mobile coverage is intermittent or absent. The runner does not need mobile data for the SPOT tracking message itself to leave the course. The device still needs normal GPS and satellite conditions, including a sufficiently clear view of the sky.
SPOT Mapping shows the location, Track3D adds the race.
SPOT Mapping can create a Shared View so friends, family and crew can follow tracking activity in near real time. If the question is simply “Where is the runner?”, that can be enough.
Ultramarathon crews usually need more than a dot on a map. They need to know where the runner is on the actual race course, which checkpoint comes next, when they are likely to arrive there, whether the Finish ETA has changed, how they are tracking against cutoff and what the crew needs to do when they arrive.
SPOT does not know the runner’s Track3D Race Plan. That is the layer Track3D adds.
| Race day question | SPOT Mapping / Shared View | Track3D Crew using SPOT |
|---|---|---|
| Where is the runner? | Shows transmitted SPOT locations and tracking activity. | Uses the SPOT location as tracking evidence. |
| Where are they in the race? | Shows a location on a map but has no Track3D Race Plan awareness. | Matches the observation to the Track3D race course and shows race progress. |
| Which checkpoint is next? | Does not derive the next Track3D checkpoint from the Race Plan. | Shows the next checkpoint from the Race Plan. |
| When will they reach the next checkpoint? | No Track3D Adaptive ETA to the planned checkpoint. | Adaptive ETA updates as new race progress arrives. |
| What is the Finish ETA? | No Track3D Finish ETA based on the live race picture. | Shows the updated Finish ETA alongside checkpoint progress. |
| How are they against cutoff? | No Track3D cutoff context from the Race Plan. | Shows cutoff status and remaining buffer. |
| What does the crew need to do there? | No Track3D checkpoint notes or crew plan. | Checkpoint notes, crew instructions and alerts travel with the race. |
| SOS and device messaging | Provided by the SPOT device and SPOT service according to the model and plan. | Track3D does not replace SPOT SOS, Help or emergency services. |
How Track3D turns a SPOT point into race progress
Track3D connects to SPOT through the XML Feed created in the runner’s SPOT account.
The customer supplies the Feed ID and, if that feed is protected, the optional feed password.
Track3D stores those details privately and uses the feed as a read only source of location observations.
The important distinction is that SPOT supplies the satellite location evidence and Track3D supplies the race model around it. A latitude and longitude becomes something the crew can act on - the runner is 74 km through the course, the next checkpoint is 9 km away and the expected arrival time has moved because their actual progress has changed.
The Feed ID and optional feed password are encrypted by Track3D and are not returned to the browser after configuration.
The customer can test the Tracker, replace the feed for future use or remove the Tracker from the account.
How to connect SPOT to Track3D before race day
The setup should be completed and tested before the race. Do not wait until the runner is standing on the start line.
- Create or identify the SPOT XML Feed. In the runner’s SPOT account, create the feed that Track3D will use and copy its Feed ID. SPOT notes that a newly created feed only returns data from the point the feed was created, so create it before the event rather than after you need historical tracking points.
- Open Track3D Trackers. In Track3D Race Planner go to Tracking → Trackers and select Configure on SPOT.
- Enter the Feed ID. Enter the optional feed password only if that SPOT feed is password protected.
- Select Save & Test. Track3D stores the configuration and tests the current connection.
- Confirm SPOT shows Ready. The feed must be active and contain at least one usable location for the readiness test to succeed.
- Run a real outdoor test. Start tracking on the actual SPOT device, let it send a real location, then confirm Track3D receives it before race day.
Seeing a point in SPOT Mapping proves only part of the setup.
The useful test is end to end: SPOT sends location, the feed receives the location, Track3D reads it, the point matches to the race course and the crew view updates.
What SPOT tracking interval should you use for an ultramarathon?
There is no single correct interval for every race. On SPOT Gen4, the standard tracking options are 5, 10, 30 and 60 minutes, with 10 minutes as the default. Extreme Tracking adds a 2.5 minute option. Service availability and battery expectations should be checked for the runner’s actual SPOT device and plan.
10 minute tracking
A practical interval for long events when the goal is a useful remote satellite picture without chasing maximum update frequency. Track3D recalculates progress and ETA when each new observation arrives.
5 minute tracking
Provides a more frequently refreshed race picture and can be a useful middle ground for crew tracking where the device and service support it.
2.5 minute tracking
Available on SPOT Gen4 with Extreme Tracking. More frequent points allow the race picture to respond sooner, but the runner should confirm service eligibility and battery expectations before choosing it.
Track3D does not require a particular SPOT interval. A slower interval can still be useful in a long ultramarathon because each genuine satellite observation is matched to the race. A shorter interval simply gives Track3D newer evidence more often.
SPOT Gen4 can suspend tracking after the device has been stationary for more than five minutes and resume when movement is detected. A long checkpoint stop can therefore create a gap in tracking points. That is normal device behaviour, not necessarily a Track3D fault.
What happens when mobile reception disappears?
This is the main reason to carry a satellite tracker in an ultramarathon. The SPOT tracking message does not depend on the runner having mobile data. If the runner leaves phone coverage and the SPOT device continues normal GPS and satellite operation, new tracking points can still be transmitted.
Track3D reads those locations server side through the configured SPOT feed, so the runner does not need a phone connection for the SPOT source itself.
The crew side is different. Track3D Crew is an online service. A crew member who is also somewhere without mobile data or WiFi cannot receive new Track3D updates until their own internet connection returns.
The runner does not need phone reception for the SPOT tracking source. The crew still needs internet to see the updated Track3D race picture.
SPOT vs Garmin inReach for ultramarathon tracking
For Track3D, both can solve the same fundamental problem: provide satellite location evidence when the runner is outside mobile coverage. The better device depends on what else the runner wants the satellite device to do.
| Consideration | SPOT Gen4 | Garmin inReach |
|---|---|---|
| Satellite race location source for Track3D | Yes, through a configured SPOT XML Feed. | Yes, through the configured Garmin tracking feed. |
| Tracking intervals | Gen4 supports 5, 10, 30 and 60 minutes, with 2.5 minutes available through Extreme Tracking. | Depends on Garmin device and subscription. |
| General two way satellite text messaging | SPOT Gen4 uses preset Check In and Custom messages plus Help and SOS functions. SPOT also sells SPOT X as a separate two way satellite messenger. | Two way messaging is a core feature of the Garmin inReach communicator range. |
| Track3D race interpretation | The same idea: Track3D matches the satellite location to the race course and updates progress, checkpoint ETA and cutoff context. | |
That distinction matters because not every runner needs every feature of an inReach Mini or another full two way satellite communicator. If the main requirement is a dedicated satellite tracking source for race day, a SPOT tracker may be a suitable option.
If the runner also wants free form two way satellite messaging, compare the communication features of the actual SPOT and Garmin models before deciding.
Track3D does not require the runner to choose one brand. The purpose of the tracking platform is to let the race location source suit the runner rather than making the runner suit one tracker.
Garmin Watch and SPOT can work together
Track3D is designed so a runner can use more than one tracking source in the same race. Garmin Connect IQ can contribute watch locations through the paired phone when suitable mobile connectivity is available. SPOT can independently contribute satellite observations when mobile coverage disappears.
Both sources are matched against the same frozen race course and contribute to the same crew view. There is no need for the crew to watch one system while the runner is in coverage and another system when they leave it.
What SPOT ultramarathon tracking is not
Satellite tracking is valuable, but it should not be described as something it is not.
- It is not continuous real time GPS. Locations arrive according to the tracking interval and can be delayed or missed by normal GPS and satellite conditions.
- It is not guaranteed in every location. Terrain, buildings, deep valleys, heavy cover and device orientation can affect GPS acquisition or satellite transmission. SPOT recommends a clear view of the sky.
- A stationary Gen4 may intentionally stop sending track points. Motion activated tracking can suspend after more than five minutes without movement and resume when the device moves again.
- Track3D is not an emergency monitoring service. SPOT SOS, Help and emergency coordination remain SPOT functions and should be used according to SPOT’s instructions.
- Track3D does not replace SPOT Mapping. SPOT Mapping and Shared Views remain SPOT’s own location sharing tools. Track3D adds race specific interpretation.
- It is not official race timing. Track3D uses location evidence to estimate race progress and ETA. Official checkpoints and timing systems remain authoritative for official results.
Why this matters to an ultramarathon crew
Imagine the runner has been outside mobile coverage for an hour. A new SPOT point arrives. A Shared View can tell the crew where that point is. Track3D can also tell them where it sits in the race, which checkpoint is next and whether the expected arrival has shifted.
If the runner has slowed through a difficult climb, the Adaptive ETA can move with the observed race. If they are moving faster than planned, the crew can see that too. The crew is no longer trying to translate a dot on a satellite map into a race plan by hand.
That is the purpose of using SPOT inside Track3D Crew: not to replace the satellite tracker, but to make each satellite location useful in the context of the race.
Frequently asked questions
Does the runner need a phone for Track3D SPOT tracking?
No. The SPOT tracking source does not depend on the runner having mobile reception. Track3D reads the configured SPOT feed server side. The crew still needs an internet connection to receive remote updates.
Can I use a SPOT Gen4 for an ultramarathon?
Yes. SPOT Gen4 can send satellite tracking points at configured intervals and can be used as a Track3D race tracking source through its XML Feed. Test the actual device and feed before race day.
Does Track3D only support SPOT Gen4?
Track3D’s SPOT integration is feed based rather than hard coded to a single device name. The important requirement is that the configured SPOT XML Feed provides usable location messages. SPOT device capabilities differ, so test the exact device and feed you intend to race with.
Do I need a SPOT Shared View?
SPOT Shared Views are useful for SPOT’s own location sharing. Track3D specifically needs the XML Feed ID used for the tracking connection, plus the feed password if one is configured.
What SPOT tracking interval should I use?
There is no Track3D required interval. On Gen4, shorter intervals provide newer race observations more often while longer intervals can suit long events where battery and service choices matter. Confirm the available interval on your actual SPOT device and plan.
Can SPOT and a Garmin Watch both be used in the same race?
Yes. Track3D can use SPOT on its own or alongside Garmin Connect IQ and Garmin inReach. Multiple valid sources contribute to the same race picture.
Does Track3D replace SPOT SOS?
No. Track3D is a race tracking and crew information service, not an emergency service. SPOT SOS and emergency functions remain separate SPOT services.
SPOT device capabilities, service plans and tracking intervals can change. Confirm the current settings for your device and service before race day. SPOT’s official Gen4 tracking guidance is available at How does tracking work? and How do I change my tracking interval?. SPOT documents its XML Feed at Public API and XML Feed.
Already have a SPOT? Start with the Race Plan.
Track3D begins with the course, checkpoints, cutoffs and timing. Track3D Crew carries that context into race day and adds SPOT satellite tracking when the runner starts moving.
Open Race Planner
Leave a comment
This site is protected by hCaptcha and the hCaptcha Privacy Policy and Terms of Service apply.