To track a dirt bike ride offline, set up while you still have signal: charge the phone, sign in, import your GPX line or plan to record the way in, choose who sees you, and start recording before the first section. Recording and the route line keep working with no bars; live positions, the regroup push and SOS do not.
This is the walkthrough we would give a friend on the night before a forest loop. It assumes you ride with a small group, the trailhead has patchy coverage, and nobody wants to pay a yearly fee just to keep a record of where they went.
What works without signal, and what needs a bar
Your phone’s GPS receiver works out its position from satellite signals and does not need mobile data for that (GPS.gov). The first fix can take longer without data, so open the app at the van while you still have a bar. Anything that only needs your own position keeps working in a dead zone. Anything that has to send data to another phone waits for coverage.
| Feature | No signal | Why |
|---|---|---|
| Ride recording (screen off) | Keeps recording | Uses GPS only |
| Following your route line, turn hints, off-route alert | Keeps working | The line is already on the phone |
| Live positions on the group map | Stops updating | Positions travel over mobile data |
| Regroup push | Does not get through | Needs signal on the sending and the receiving phone |
| SOS to your group and riders nearby | Cannot be sent | Needs a phone signal |
| Map background | Do not count on it | Carry a backup map source |
The last row matters. If you want a full topo map in a valley with no coverage, that is a job for a dedicated mapping app or a paper map, and it is worth having as a second layer anyway.
What offline trail apps charge for
In many trail apps, offline maps are the paid feature. As of October 2026, onX Offroad’s pricing page lists a free version that can save one offline map, a $34.99-a-year tier with unlimited saved maps, and a $99.99-a-year tier that adds property boundaries and landowner names. If you ride public land in the US and want land boundaries in a dead zone, that is a fair trade.
Ridekin does something narrower. It is free, no ads, nothing to buy; Android now, iOS coming. It records your ride, follows a GPX line you bring, and, when there is signal, puts your group on one live map and sends SOS to your group and opted-in riders nearby. It has no trail database and no legality check, so you confirm access rules yourself. The Tread Lightly principles put this as “Educate yourself”, and that part is on you.
The setup before the trailhead, step by step
Do steps 1 to 5 at home on Wi-Fi. The rest takes two minutes in the car park.
- Charge the phone and a power bank the night before. Recording uses GPS for hours, so battery use rises. A short cable that reaches the bar mount beats a long one that snags.
- Install the app and sign in at home. Signing in needs a connection. The trailhead is the worst place to find out your password manager wants a code by text.
- Let the app run in the background. On Android, open the app’s battery settings and allow unrestricted background use, so the system’s power saving (Doze and App Standby) does not pause the recording when the screen goes off.
- Import your GPX line, or decide to record the way in. Import a track, not a route, so the line follows the trail as drawn. If you are unsure which you have, the GPX track vs route guide explains the difference in a few minutes.
- Start or join the group ride while you have signal. The leader shares the invite link in your usual messenger, and can load the route line for everyone.
- Choose who sees you. Visibility is hidden by default. For a trail ride, “my group” is usually enough. “Group + riders nearby” also shows you to riders nearby as an area of about a kilometre, never a pin. Pick a timer: 1 h, 4 h or until I stop.
- Start recording before you roll. Start it in the car park, then lock the screen. The recording keeps going with the screen off.
- Follow the line. You get turn hints and an off-route alert when you drift away from the line. The app does not calculate a new route; if the alert fires, ride back to the line or stop and check.
- Stop the recording at the van and export the GPX. Then decide who should have it.
After the ride: export the GPX and share it without posting it
A good loop often crosses private land with permission, or reaches a spot the locals would rather keep quiet. Treat the recording like a key to that loop.
Export the GPX file and send it to the riders who need it. If you share the ride link instead, remember that anyone who has the link can open the ride page, so send it in a direct message, not in a public group or on a forum. Ridekin has no feed and nothing is published unless you pass it on.
The export is also useful next weekend. Import last week’s recording as the line to follow, and the off-route alert will tell you when you have missed the turn you missed last time. For more on following a line off-road, read how to follow a GPX line off-road without rerouting.
SOS on a trail: what it can and cannot do
SOS in Ridekin is a button you press yourself. It alerts your group and riders nearby who opted in, and it needs a phone signal to go anywhere. It is not an emergency service, it does not call 112 or 911, and it has no crash detection. If someone is hurt, call your local emergency number first, then use SOS to tell your group where you are.
In a true dead zone, SOS cannot be sent at all. That is why the plan you leave with someone at home still matters more than any app. The enduro pre-ride checklist covers that plan.
From the road
Picture the morning this setup is built for. Four riders, a forest loop of about 60 km, one bar of signal at the car park and none after the first climb. One rider imported last month’s recording as the line and started recording at the van. Two hours in, a fallen tree blocked the fire road, and the group took a detour on a track none of them knew. The off-route alert fired as soon as they left the line, and they rejoined it a few kilometres later instead of guessing. Nobody saw anyone on the group map until the ridge, where the bars came back for five minutes. The recording had no gap.
Common mistakes
- Signing in at the trailhead. With one bar, a login that wants a code by text can hold up the whole group.
- Importing a route instead of a track. A route is a list of points that another app was supposed to connect; a track is the line itself.
- Leaving battery saving on. Some Android phones pause background apps aggressively. Allow background use before the ride, not after the first gap.
- Expecting the group map to work in the valley. It updates when phones have signal. Agree regroup points anyway; the group riding guide covers how.
- Posting the GPX in a public group. Once a file is out, you cannot pull it back.