GPS running distance differs from the real route because your device only knows a string of position fixes, each a few metres out, joined by straight lines. On open roads the errors mostly cancel and the distance comes out close. On winding trails, GPS tends to cut corners and read short. In races your watch usually reads long, because courses are measured along the shortest possible line and nobody runs it. Your pace is worked out from that distance, so every distance error shows up in your pace too.
This page is about total distance. If it’s the live pace number that’s bothering you, see why GPS pace jumps.
How does a GPS app measure running distance? #
About once a second, your phone or watch works out where you are. Each fix has an error, typically a few metres under a clear sky and more under trees or between buildings. The app adds up the straight lines from each fix to the next, and that’s your distance.
Two opposite errors come out of that:
- Jitter adds distance. Noisy fixes wander either side of your real path, and a wiggly line is longer than a straight one. It’s worst when you’re moving slowly or standing still.
- Corner-cutting removes distance. A straight line between two fixes shortcuts every bend in between. The fewer fixes a device records, the more it cuts, which is why battery-saving recording modes make twisty routes read short.
Apps filter jitter, and the filter itself can cause trouble. A filter tuned for cars, like the one in a speedometer app, throws away small steps between fixes, and at running speed most of your steps are small. More on that below.
Why is my GPS distance longer than the race distance? #
Certified road courses are measured along the shortest route a runner could legally take, cutting every corner tight. Measurers usually use a calibrated bicycle, not GPS.
Nobody runs that line. You swing wide round corners in a crowd, weave past slower runners, drift to the side for water and cross the road for shade. Each detour is small, but over a half or full marathon they add up, so it’s normal for a watch to show a few hundred metres over the official distance. Tall buildings in city races add GPS error on top, because reflected signals make the recorded track zigzag.
For pacing, that means the watch’s average pace is a little faster than your real pace over the course. Pace by the course markers, not the watch’s auto-laps.
Why is my GPS distance shorter on trails? #
Trails combine everything GPS dislikes:
- Switchbacks and tight bends, which straight lines between fixes cut off.
- Tree cover, which weakens signals and makes each fix less precise.
- Steep ground. GPS measures distance flat, as if the trail were drawn on a map. On a 10% grade the real distance along the slope is only about 0.5% longer; on a 20% grade it’s about 2% longer.
Under heavy canopy the jitter can win instead, and the trail reads long. Which way it goes depends on the day, the device and the route. Our hiking trail distance guide covers trails in more detail.
What to expect on different routes #
| Where you run | Usual error | Why |
|---|---|---|
| Straight, open road | Very close | Clean signals, few bends |
| Neighbourhood loop with trees | Slightly short or long | Canopy adds noise; corners get cut |
| Road race with crowds | Long vs the official distance | You don’t run the shortest line |
| City centre with tall buildings | Often long | Reflected signals zigzag the track |
| Winding forest trail | Often short | Corner-cutting and weak signals |
| Standard 400 m track | Varies lap to lap | Tight bends; outer lanes are longer than 400 m |
| Standing at lights with tracking on | Long, unless filtered | Drift while stationary |
How much GPS distance error is normal? #
There’s no single figure, because the route matters more than the device. On an open road with a good fix, a phone or watch usually lands close to a measured distance, and a spread of a few tens of metres on a 5 km loop from day to day is normal. Errors of several percent usually mean a hard route (dense trees, tall buildings, lots of tight turns) or a weak signal. If a device is consistently off by a lot even on open roads, check how it’s carried and how often it records. Phones and watches differ mainly in antenna placement and recording settings; we compare them in phone GPS vs running watch.
How to check your GPS against a known distance #
- Use a track. Four laps of lane 1 on a standard 400 m track is 1,600 m, just 9 metres short of a mile. Stay in lane 1; outer lanes are longer.
- Use a certified course or measured path. Many parks have marked loops. Run the tangents yourself to get close to the measured line.
- Repeat it. One run tells you little. Three or four on the same route show which way your device errs and by how much.
- Look at the route, not just the number. On a map, a track that cuts across corners means short; one that zigzags means long.
Can a GPS speedometer app measure a run’s distance? #
Not accurately, and you should know why before you try. Speedometer GPS is built for vehicles, boats and bikes. To stop a parked phone from inventing distance, it ignores steps of less than 5 metres between one-second fixes, drops fixes worse than ±20 m, and only adds distance while you’re moving. At running speed you cover roughly 2.5 to 4 metres a second, so most steps fall under that filter and the trip distance comes out far short. It only counts normally above about 18 km/h (11 mph).
What still works: its live speed and average speed come from the GPS receiver’s own speed measurement, so average speed × moving time gives a fair distance estimate. It also records every GPS point along the way even when the distance counter ignores it, so the saved route shows where you went, and you can export it as GPX (thinned to 500 points) for another program to measure. For real running distance, pace and splits, use a running app or a GPS watch.
How to get a more accurate running distance #
- Start with a good fix. Wait 20 to 30 seconds in the open before you press start.
- Record every second if your watch lets you choose.
- Carry the phone where it can see the sky, on an armband or waist belt rather than deep in a pack.
- Pause, or let auto-pause work, at long stops, so drift doesn’t count.
- In races, lap at the markers, and treat the watch’s total as your distance, not the course’s.
If your pace looks odd, check the distance first: the pace vs speed guide shows how a distance error flows straight into pace.
Frequently asked questions #
Why does my watch show more than 42.2 km after a marathon? #
Marathon courses are measured along the shortest possible line. You run wider than that around corners and crowds, and GPS adds small errors of its own, so the watch counts extra distance. By the watch, your pace will look faster than your official pace.
Is GPS or a footpod more accurate for running distance? #
Outdoors on open roads, GPS is usually better because it needs no calibration. A calibrated footpod is better on tracks, tight trails and indoors, where GPS struggles. Many runners use a footpod for speed and GPS for the route.
Why does my running app add distance while I’m standing still? #
A stationary phone’s position drifts by a few metres, and an app that doesn’t filter that drift adds it up. Apps that ignore tiny moves and only count distance while you’re moving avoid most of it, though a filter set too coarse will also cut real running distance.
Does running uphill make GPS distance shorter? #
Slightly. GPS measures distance as if the ground were flat, so on hills the real distance along the slope is a little longer. On moderate hills it’s under 1%; it only becomes noticeable on very steep trails.
Why is my GPS distance different every time I run the same route? #
Satellite positions, trees in leaf, weather and exactly where you run all change from day to day, so the errors change too. Average several runs if you want to know the route’s length.