Why does my friend's location say it was updated 15 minutes ago?

Because phones do not send a continuous stream. Between fixes the map shows the last known position with its timestamp. A gap of several minutes is normal for a phone in a pocket, especially when the person has not moved much, is indoors, or is in a low-power state.

Does a stale location mean something is wrong?

Usually not on its own. A stale pin means the phone has not reported recently, which happens for battery, signal and operating-system reasons far more often than for safety reasons. What makes silence meaningful is pairing it with a timed check-in, so there is an expected response at an expected time.

Is a location pin accurate to the exact spot?

No. Every fix carries an accuracy radius. A good GPS fix outdoors may be accurate to a few metres, while an indoor fix derived from Wi-Fi or cell towers can be off by tens or hundreds of metres. The dot on a map is the centre of an estimate, not a precise position.

Why a location pin goes stale — and what "last seen" really means

Someone shares their location with you. You open the map, see a dot, and feel informed. Then you notice the small grey text: updated 14 minutes ago. This guide explains what that timestamp is telling you, why it is usually not alarming, and what would make it alarming.

A shared location is a timestamp, not a video feed

The mental model most people bring to a location share comes from films: a blinking dot moving smoothly across a map in real time. That is not what any consumer phone does. What actually happens is that the phone occasionally computes a position and sends it to a server, and the map draws the most recent one it received. Between those moments the dot is frozen — not because anything is wrong, but because there is nothing new to draw.

So a location share always carries two pieces of information, and the second one is the one people ignore:

Where the phone last reported being.
When it reported that.

A pin without a timestamp is close to meaningless. A pin from four seconds ago and a pin from four hours ago look identical on a map and mean entirely different things.

Why gaps happen

Cause	What you'd see	How concerning
Phone is stationary	Same position, timestamp creeping forward slowly	Normal. Many systems deliberately send fewer updates when you aren't moving, to save battery.
Phone in pocket, screen off	Updates every few minutes rather than continuously	Normal. The OS is throttling background work by design.
Indoors, underground, dense city	Position jumps around; accuracy circle grows	Normal. GPS is weak indoors, so the phone falls back to Wi-Fi and cell positioning.
Low Power Mode / Battery Saver	Noticeably longer gaps	Normal but worth knowing — both platforms cut background activity in these modes.
No signal	Position frozen at the last place with coverage	Normal in rural areas, lifts, tunnels, basements. The phone may know where it is and simply be unable to say so.
Battery died	Hard stop, no further updates at all	Common and mundane — but indistinguishable from the serious cases without more information.
App was force-quit or killed by the system	Hard stop	Common. See how background location works.
Something is actually wrong	Hard stop	Rare — but this is the case the whole system exists for.

The uncomfortable point in that table is that the last four rows all look the same from the outside. A frozen pin does not tell you which one you are in.

Accuracy is a radius, not a point

Every location fix comes with an accuracy estimate, and it varies enormously by how the position was derived. A clear outdoor GPS fix might be good to a handful of metres. A fix computed indoors from nearby Wi-Fi networks might be good to fifty metres. A fix from cell towers alone can be off by hundreds of metres or more.

This is why a pin sometimes appears to be in the building next door, or on the wrong side of a street, or briefly jumps a block and comes back. That is not the app lying — it is the underlying estimate changing as better or worse signals become available.

Reading tip: when a map shows a shaded circle around a dot, the person is somewhere in that circle, not at its centre. A large circle is the map being honest with you.

The fix for ambiguity is not a better map

If you only have a location stream, silence is ambiguous forever. You cannot resolve "dead battery" versus "in trouble" by staring harder at a pin, and refreshing does not create data that was never sent.

What resolves it is adding an expected response at an expected time. That is what a timed check-in does: the person agrees in advance that they will confirm they're fine every N minutes. Now silence is no longer ambiguous — it is a specific, pre-agreed failure to answer a specific question, and it can trigger a specific action. The location data becomes the supporting evidence rather than the whole signal.

A good system also builds in a grace period, because the most common reason to miss a check-in is being mid-conversation, not being in danger. In SafeMeet a missed prompt starts a 60-second silent countdown before anyone is notified.

Practical guidance for the person watching

Read the timestamp first, the pin second. "Where" without "when" is not information.
Set expectations before they leave, not during the gap. Agree what "on time" looks like.
Don't escalate on a five-minute gap. That is ordinary phone behaviour, and reacting to it teaches everyone to ignore the system.
Do escalate on a missed check-in, especially combined with a long location gap. That combination is what the system is designed to surface.
Try the boring explanation first. Call them. A ringing phone that goes to voicemail tells you something; a phone that is off tells you something else.

If you are the person being watched, the kindest thing you can do is tell your contact in advance what normal looks like — which is exactly what what to tell your trusted contact is about.