What if the course were flat?
The recorded elevation profile is normalised to 0 m on a level course while keeping the effort represented by each timed segment.
Timed elevation data is needed for this estimate.
Open a GPX, FIT, or TCX activity exported from Garmin Connect, Strava, or another running app. See the data your watch recorded without creating an account or uploading the file.
One activity at a time, up to 25 MB. Running, walking, hiking, and trail files are supported.
or select a file from your device
Your file and GPS route stay in this browser tab.
Distance, moving and elapsed time, average pace, elevation gain, kilometre or mile splits, heart rate, and cadence—depending on what your device included in the export.
—
Moving time excludes sustained stops detected from timestamped track points. Results can differ from the source app's proprietary calculations.
Values across the recorded distance.
—
Generated from cumulative activity distance.
| Split | Time | Pace | Δ |
|---|
Compare this recorded performance with a level course and standard race distances.
The recorded elevation profile is normalised to 0 m on a level course while keeping the effort represented by each timed segment.
Timed elevation data is needed for this estimate.
Equivalent finish times use this activity's distance and moving time in the RunCalcs race predictor.
How to read this: the flat scenario uses smoothed 50 m segments and the grade-energy relationship measured by Minetti et al.; it does not account for terrain, wind, weather, altitude, fatigue, or downhill skill. Race conversions use the Riegel model (exponent 1.06). Treat both as planning estimates, not guaranteed results. Grade model source.
Editorial check: completed by the RunCalcs Editorial Team.
Coverage and anomaly checks show which results have enough recorded data to interpret.
Compare the two halves and the consistency of complete kilometre splits.
More timed distance is needed for pacing insights.
A 50 m sampled profile reduces the effect of point-to-point altitude noise.
Review peak heart rate, relative bands, efficiency drift, and the relationship between speed and heart rate.
Heart-rate analysis appears when enough timed sensor data is available.
Editorial check: completed by the RunCalcs Editorial Team. Relative bands describe this file and are not medical advice or a substitute for individually tested training zones. For a personalised calculation, use the heart-rate zones calculator.
GPS track from this activity.
This is a shape-only preview, not a navigational map. Coordinates remain in this browser tab and no third-party map service is contacted.
GPX is primarily a GPS route format. It usually contains timestamps, coordinates, and elevation, but sensor data varies by app.
FIT is a compact binary fitness format commonly produced by sports watches. It can include distance, laps, heart rate, cadence, power, temperature, and device-specific fields.
TCX is an XML training format. It commonly includes GPS points, elapsed time, distance, heart rate, cadence, and laps.
The analyser uses the track points available in the file. GPS noise, tunnels, pauses, smart recording, barometric corrections, and differences between moving-time algorithms can make these results differ from Garmin Connect, Strava, or your watch.
Editorial check: completed by the RunCalcs Editorial Team. This tool describes recorded activity data and does not assess fitness, health, or injury risk.