Route Performance History Comparison
Runners and riders: load last month's GPX and today's, and see the difference honestly — distance, time, average pace, elevation gain and average heart rate where the file records it. Files never leave your browser.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, last month's 10.02 km in 52:30 (5:14.4/km) against today's 10.05 km in 50:12 (4:59.7/km) is 14.7 seconds per kilometre faster — a 4.67% improvement the comparison computes, not vibes.
How to use Route Performance History Comparison
Same route, two days, one honest table:
The Route Performance History Comparison loads two GPX files — an earlier effort and a later one — and compares distance, time, average pace, elevation gain and average heart rate where recorded. Your files never leave the browser; the comparison is computed locally from the two recordings you choose.
- 1Drop the earlier GPX as Performance A.
- 2Drop the later GPX as Performance B.
- 3Compare the table and download it as CSV if you want.
What people use Route Performance History Comparison for
1. Training progress checks
Monthly benchmark efforts on one course are the runner's controlled experiment. This comparison is its lab report — feed the files from the GPX Route Stats family you already trust.
2. Pacing strategy reviews
Was the faster day faster early or late? Average pace plus the elevation context starts the answer; segment tools finish it.
3. Equipment comparisons
New shoes, new bike setup, same loop: the pair of files either supports the purchase or politely doesn't.
4. Comeback tracking
Post-injury rebuilds measured against the pre-injury baseline — heart rate at matched pace is the number coaches watch first.
Worked examples
March: 10.02 km, 52:30 → 314.4 s/km (5:14.4). April: 10.05 km, 50:12 → 299.7 s/km (4:59.7). Difference: 14.7 s/km, 4.67% faster — at similar heart rate, that is fitness; at much higher heart rate, that is effort. The comparison shows both, because one without the other misleads.
If the two files differ by 400 m, they are not the same route or one GPS cut a corner. Compare paces only when distances roughly agree — the tool shows both distances precisely so this check is yours to make.
The comparison, field by field
What is compared, and how to read each row.
| Field | Compared as | Reading |
|---|---|---|
| Distance | km/mi, both files | Must roughly match for a fair fight |
| Moving/total time | From timestamps in the files | Pace's denominator |
| Average pace | Time ÷ distance, per km and per mile | Lower is faster — the headline |
| Elevation gain | Summed climbs per the file's ele data | A hillier day excuses a slower pace |
| Average heart rate | Where <extensions> or HR data exists | Effort's witness — pace without it is half the story |
Both files must contain the fields being compared. Missing heart rate or elevation in one file narrows the comparison to what both honestly hold.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Route Performance History Comparison:
- Validate before trusting exports from unfamiliar tools — open them in a local viewer and check feature counts, bounding boxes and a few property rows. A wrong-axis or swapped-coordinate export is far easier to catch on a map than in a spreadsheet.
- For big CSVs, fix the coordinate columns first and map a sample before mapping everything: auto-detection is good but not magical, and one swapped column renders a beautiful map of the wrong ocean.
Limits & appropriate use
File formats support different combinations of geometry, timestamps, properties and styling. Converting between them can lose information, so keep the original and inspect the output before sharing or using it.
Capabilities differ by workspace: check the accepted format and the operations actually offered on this page. Some tools process files locally but may request map tiles or other services over the network; large or specialised datasets may require dedicated GIS software.
- Cadastral/legal formats → jurisdictional land-registry exports.
- Point clouds and rasters → desktop GIS with proper spatial indexes.
- Certified tracks (evidence, insurance) → chain-of-custody originals, untouched.
Data & methodology
Local DOMParser GPX parsing; haversine distance, recorded-time pace, elevation-gain summation and extension heart-rate averaging.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Bounding box
- The minimal rectangle enclosing a dataset; the instant sanity check.
- GeoJSON
- JSON geographic format; the web-mapping native dialect.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Map Files. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- Local DOMParser GPX parsing; haversine distance, recorded-time pace, elevation-gain summation and extension heart-rate averaging.
- Before relying on the answer
- Inspect the accepted file format and the fields reported by this specific tool. Keep a copy of the original file before converting or editing it.
- What the result cannot establish
- File geometry and recorded timestamps can be incomplete. Verify row or point counts and inspect the exported file in your target application.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Where is my history stored?
Nowhere on MapBench — “history” means the GPX files you keep. Both are parsed locally in your browser and nothing is uploaded.
What if a file has no heart rate?
The comparison says “not in file” for that row instead of inventing a value.
Is my uploaded map file sent to a server?
Where a page says browser-first or local processing, the file is handled in your browser. Check the individual tool note for any external-service dependency.
What should I do if a file will not load?
Check that the file type is supported, the structure is valid and the file is within the stated size limits. Converting to GeoJSON, GPX, KML or CSV can also help.
Will converting a file preserve every property?
Not always. Geographic formats support different geometry, style and metadata features, so inspect the output before relying on it.
Do the files need to be the same route?
The comparison works on any pair, but it means something only for the same course in the same direction. Different routes compare numbers; same routes compare performances.
One file has no heart rate.
Then heart-rate rows compare as absent — the rest of the comparison stands. Many watches record HR only with a strap or optical sensor enabled.
Moving time versus total time?
Files with pauses contain both stories. The comparison uses the file's recorded spans consistently for both efforts — consistency matters more than the choice.
Elevation gain differs between my watch and this.
Gain algorithms differ (thresholds smooth small bumps differently). Comparing two files under one algorithm here is fairer than comparing two devices' own summaries.
The distances differ by 2%.
GPS variance on identical routes runs 1–2% normally. Paces computed per-file remain comparable; treat sub-1% pace differences as noise.
Can it compare a plan against an effort?
A route file (plan) against a track (effort) compares distance and elevation only — no times exist in a plan. Still useful for course-checking.
Where does 'history' live?
Nowhere but your files. There is no account and no stored history — your archive is your history, which is why the comparison asks for two files each time.
Related tools and resources
One file's stats: GPX Route Stats; speed focus: the GPX Average Speed Calculator; heart rate: the GPX Heart Rate Analyzer; gain: the GPX Elevation Gain Calculator.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our routes & travel time hub
Route Performance History Comparison sits in the routes & travel time cluster, alongside 62 other tools that answer neighbouring questions with different methods or datasets.
Elsewhere in this cluster
The same family of methods, so a comparison between two results is meaningful rather than apples-to-oranges.
- Running Route Loop Generator
Generate a loop run or ride of about the length you want, from your door.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Radius vs. Drive Time vs. Straight-Line Distance: Which Map Should You Use? — A practical guide to choosing between a radius circle, road travel-time map and straight-line distance so your result matches the real question you are trying to answer.