Free Tool
GPS Watch Distance Error Calculator
Enter a known course distance and what your GPS watch recorded. The calculator returns the signed difference, percentage error, and whether the watch over- or under-recorded — with an optional corrected average pace if you add elapsed time.
Percentage error
—
Over- or under-recording
Signed difference
—
Absolute error
Corrected average pace
—
From known distance and elapsed time, not the watch distance
Enter your numbers to see the result. Everything updates as you type.
Create a valid baseline
The percentage is only as honest as the known distance. Prefer a course measured independently of the watch: a USATF- or World Athletics-certified road race, a standard 400-meter outdoor track in lane 1, or a route measured with a surveyor's wheel or calibrated bike computer. Repeat the same course on more than one day and in similar satellite conditions.
A neighborhood loop you traced on a map is a weaker baseline. Map tools can be close, but they are not a certified measurement, and you may not run the same tangents each time. Indoor tracks and treadmills are the wrong test for outdoor GPS; use track mode or a foot pod there instead.
What one result can and cannot show
One comparison answers a narrow question: on this activity, against this baseline, did the watch read long, short, or even? It can tell you whether today's file is usable for pacing, and whether a setting change (1-second recording, a longer lock, track mode) moved the error.
It cannot prove the watch is defective, predict the next run, isolate a single cause, or replace a certified race measurement. Apps may also rewrite distance after upload, so the number on your wrist and the number in Garmin Connect, COROS, Strava, or Apple Fitness can disagree even when the hardware file is unchanged.
Why GPS watch distance goes wrong
| Cause | What usually happens | Typical direction |
|---|---|---|
| Poor satellite lock | Starting under a roof, in a canyon, or before enough satellites are visible | Either; often messy at the start |
| Tree canopy | Leaves and branches weaken or block signals on trails and cross-country courses | Wander, then over- or under-record |
| Urban multipath | Signals bounce off glass and concrete before they reach the watch | Often over-records |
| Turns and tracks | The watch connects dots and can cut the infield or add zigzags on curves | Short on tracks; mixed on switchbacks |
| Battery-saving sampling | Smart or ultra recording stores fewer points and misses corners | Often under-records on winding routes |
| App recalculation | The phone app or Strava may recompute distance from the GPS track after upload | Watch and app no longer match |
Fix checklist by symptom
Always long on open roads. Wait outside for a lock before pressing Start, wear the watch above the wrist bone, use 1-second recording if the watch offers it, and compare the watch file to the app. Position jitter and post-upload smoothing are the usual suspects.
Always short on a winding path. Turn off battery-saver or ultra GPS modes. Sparse samples draw straight lines across corners. Repeat the same loop at 1-second recording before you blame the chipset.
Fine on roads, messy on a 400 m track. Use the watch's indoor or outdoor track mode, or a calibrated foot pod. Dual-band GPS is not the main fix for lane geometry.
Random from day to day. Check canopy, downtown reflections, starting indoors, and whether the app rewrote the file. One wild day is not a device verdict; a repeatable bias is a settings or environment problem.
Watch and Strava (or Connect) disagree. That is often app recalculation, not a second measurement. Decide which number you will log and stay consistent. See Strava's note on how it calculates distance after upload.
When dual-band GPS, track mode, a foot pod, or a barometer matters
Dual-band / multi-band GPS can tighten the route near buildings, trees, and mountains by using a second civilian signal. It is worth reading our guide to whether dual-band GPS accuracy is worth it if your error shows up in those places — not if your usual loop is open suburban road.
Track mode (or a calibrated foot pod) is the right tool when the known distance is a 400-meter track or treadmill. GPS dots do not follow lane 1 well. A foot pod also helps when you need indoor distance without inventing a satellite track.
A barometric altimeter does not correct horizontal distance. Use it when the problem is ascent, altitude, or hill volume. Start with whether you need a barometric altimeter in a running watch and the GPS watch elevation fix checklist if climbing numbers are the issue.
Formula, examples, and limitations
Percentage error uses only this identity: (watch distance − known distance) ÷ known distance × 100. The same units must be used on both distances. Convert first if your watch and the course card disagree (miles vs kilometers vs meters). The ratio — and therefore the percentage — does not change when both values are converted together.
- Known 5.00 km, watch 5.15 km → +0.15 km, +3.00%, over-recording.
- Known 400 m, watch 392 m → −8 m, −2.00%, under-recording.
- Known 10.00 mi, watch 10.00 mi → 0, 0.00%, exact match for these inputs.
- Optional pace: 25:00 on a known 5.00 km is 5:00 /km (8:03 /mi), even if the watch thought you ran 5.15 km.
This tool does not invent terrain factors, sample-rate multipliers, or brand-specific corrections. Those would look precise and still be guesses. If you want a training pace from a known distance, use the running pace calculator.
Sources: GPS.gov on GPS accuracy; Garmin FAQs on GPS distance, speed, and pace; Apple Watch workout calibration; COROS GPS mode guidance; Strava on how distance is calculated; Johansson et al., GPS sport-watch distance in an ultramarathon; Ranacher et al. on why GPS distances tend to read long.
Related GPS and watch guides
When the climb total is wrong, not the distance. Calibration, dirty ports, and app elevation correction.
Dual-band GPS: is it worth it?When a second frequency helps city, forest, and mountain tracks — and when it does not.
Barometric altimeter buying guideElevation is a different sensor. Read this before paying extra for climb data.
Youth XC and track GPS watchesComfort, battery, and simple controls for school courses — including wooded cross-country.
Running pace calculatorSolve pace, time, or distance once you trust the distance you are using.
Wearables & GPS watchesHub for kids activity trackers and the watches that record these workouts.
Frequently asked questions
How do I calculate GPS watch distance error?
Subtract the known course distance from the watch-recorded distance, then divide by the known distance and multiply by 100. A positive percentage means the watch over-recorded; a negative percentage means it under-recorded. This tool uses only that arithmetic.
How accurate is my GPS watch?
Consumer GPS watches are often within about 1% to 3% of a trusted baseline in open sky, and can drift more under trees, between buildings, on tight turns, or when the watch samples less often to save battery. One activity is a snapshot, not a verdict on the device.
What is a valid baseline for a GPS watch distance test?
Use a certified road-race course, a standard 400-meter outdoor track (lane 1), or another independently measured route. Repeat the same course on more than one day. A map-traced neighborhood loop is a weaker baseline than a surveyed or certified distance.
Why does my GPS watch over-record or under-record distance?
Common causes include a weak satellite lock, tree canopy, urban multipath (reflected signals), cutting or adding corners on turns, battery-saving sampling, and an app recalculating distance after upload. Over-recording often comes from position jitter; under-recording often comes from corner-cutting or sparse samples.
Does dual-band GPS, track mode, a foot pod, or a barometer fix distance error?
Dual-band GPS can help near buildings, trees, and mountains. Track mode or a foot pod is the better fix on a 400-meter track. A barometric altimeter improves elevation, not horizontal distance. This calculator does not apply any of those as correction factors.