Trail Radar

Most safety apps go quiet when the trail does.

The trail you actually want to be on is the one where your phone stops working. The ridge past the last bar. The river bend that swallows cell. The thirty minutes into a forty-minute loop where the dot stops moving — because the dot stopped updating, not because you did.

Every consumer safety app assumes you can press a button. Every check-in app assumes you have a signal. Out here, both assumptions break at the same time. The button is in your pocket; the signal is two miles back at the trailhead. The person waiting for the text is doing the only thing they can do — staring at a dot that hasn’t moved for an hour.

Set the route. Set the deadline. The mesh does the rest.

Tell your people you’re starting a run. Drop the route, the distance, and a return time. From that moment your phone is doing two things: holding the route on-device, and broadcasting your last known position through the human mesh — to other phones near you, to a single trusted contact, and (optionally) to the local search-and-rescue dispatch you’ve pre-authorized.

If you come back inside the window, the run closes itself. Your contact gets the “back safe” text. No buttons pressed.

If you don’t, the mesh has already done the hard part. Your contact gets your last confirmed position, the route you committed to, the time the signal dropped, and a clean handoff to SAR — not a screenshot of a frozen dot, but a structured trace SAR can act on without translation.

Built for the people whose route changes after the last bar of signal.

Trail Radar is built for the runner who keeps going past the marked loop, the hiker who improvises around a closed switchback, the SAR-track-runner training for a race, the parent doing a solo morning hike before the day starts. It is the same architecture as Walk-Home Radar — committed route, timed deadline, mesh-resilient check-in — translated to the geometry of a trail instead of a sidewalk.

It assumes the things a real trail run actually assumes. That the route will change. That the phone will lose signal for stretches. That nobody wants to carry a satellite messenger for a Tuesday morning loop. That the person at home wants one text, on time — not a tracking app they have to babysit.

The SAR layer underneath.

Trail Radar is built around the data structure search-and-rescue coordinators already use. The committed route, on-trail breadcrumbs, and last-confirmed position the system captures are the same inputs a coordinator builds by hand in the first thirty minutes of a callout. The goal is to hand it over already built.

The hand-off is opt-in and one-way: nothing leaves your phone until your declared window expires, and then only the minimum SAR needs to act — route polyline, last position, declared return time, who to call first. Your daily run is not a tracking subscription. Your overdue run is a search grid with a head start.

For SAR teams running the call, the human mesh changes the math. The recoveries that take days because the search area was a square mile of “somewhere on the ridge” are recoveries that take hours when the route was already on the map. The data is yours; the speed is theirs.

The shapes of the stories — and what would have been different.

• The Tuesday loop. Forty-minute run. Signal dies twenty minutes in. The fall is at twenty-six. At thirty-eight, the partner at home opens the app and sees the dot frozen at the last good position; at forty-five, the run is overdue and the partner has the route polyline ready for the dispatch call. The 911 call gets a search grid, not a “she said she was going running.”
• The river bend. A solo hiker takes the unmarked spur off a marked trail. The cell-tower line and the spur diverge at the river bend; the last good position is upstream of where they actually are. Without the route polyline, search starts at the last ping. With the polyline, search starts at the spur — saved hours, possibly saved life.
• The run that closes itself. Forty minutes. No signal for stretches. Nothing wrong. The partner at home opens the app once at minute thirty-five, watches the polyline tick along the committed route, closes the app, and never thinks about it again. The “back safe” text lands at minute forty-two. This is the case the system is built to make boring — because if every uneventful run is boring, the one that isn’t gets answered fast.

The layer between the trailhead and the SAR truck.

Trail Radar is shaped by the gap the existing tools leave: consumer trail apps are designed for the trailhead, not the ridge; SAR-grade trackers are designed for the team, not for the person whose route is changing in real time. Trail Radar is the layer in between — the one that produces SAR-ready data without making the runner carry a SAR-grade device.

The trail is already on your phone. Let your people — and the people who would come looking — see you on it.

Try Tripwire Recon on the App Store. The Trail Radar workflow lives inside the same human-mesh app the rest of the safety pillar is built on. Talk to us if you coordinate a SAR team or run a trail-running club and want to plug your routes and trailheads in.

See also: the safety pillar; Walk-Home Radar; Group Radar; the platform.