Using GPS Pace Tracking to Improve Your Running
Pace is just speed turned inside out. Here is how to read it well and avoid the most common GPS running mistakes.
Pace is the inverse of speed
Where cycling and driving usually care about speed (distance per hour), running is usually measured as pace — time per distance, like minutes per kilometer or mile. Both come from the same underlying GPS speed reading, just expressed differently.
Why pace jumps around on a run
Short-term pace estimates are sensitive to GPS noise, especially at the start of a run before your position has settled, or in areas with tall buildings or heavy tree cover. Average pace over the whole run is much more stable than instantaneous pace.
Practical tips
- Start your tracker a few seconds before you start running, not at the exact moment you take off
- Expect the first 10 to 20 seconds of pace data to be noisy
- Use average pace, not instantaneous pace, to judge your effort over a run
- On a track or treadmill, trust the known distance over GPS, since GPS does not work indoors or reliably on tight repeated loops
Setting realistic goals
Small pace variations from GPS noise are normal and do not reflect your actual effort. Look at trends over weeks, not second-by-second numbers.
Try it yourself
Running Pace Tracker — free, no install, works in your browser.
Frequently asked questions
Should I trust GPS pace on a treadmill?
No — GPS does not work indoors. Use the treadmill's own speed and distance readout instead.