Ride stats
Open any ride with Full stats — from the three dots in My Rides or from its card on the calendar; both doors use the same name. You get distance across the top and a grid of numbers under it. Some of them are blank on files imported from other apps, and there’s one number that reads differently here than it did when you finished the ride.
Distance is the headline. Under it, duration and average speed, then top speed and total climb.
Two more cards appear only when they have something to say: Break Time when the ride was auto-paused at least once, and Hard Braking when the ride caught at least one hard stop.
What each number is
- Distance — added up point to point across the whole recording. Under a kilometre it’s shown in metres.
- Duration — the clock time from the first point to the last, breaks included.
- Avg Speed — distance divided by that clock duration. Because breaks are in the duration, a day with long stops gives a low average.
- Max Speed — the single highest speed reading in the file.
- Elev. Gain — every rise between consecutive points added together. Only rises of more than three metres count, which keeps GPS wobble out of the total. It’s shown in metres, always.
- Break Time — how long the recording spent auto-paused. Only shown when there was at least one break.
- Hard Braking — how many hard-braking events the ride caught. Only shown when there was at least one, and only while your subscription is active.
The Ride Complete box takes your breaks off and shows you moving time. This screen shows the whole elapsed time, breaks included, with the stopped portion listed separately as Break Time. The same ride will genuinely show you two different durations and two different average speeds. Neither is wrong — one answers “how long was I riding”, the other answers “how long was I out”. If you want moving time here, take Break Time off Duration.
Why some numbers show a dash
Open a GPX imported from another app and Duration, Avg Speed and Max Speed all read — in grey, with a line at the bottom of the screen saying Speed & duration not available for imported GPX files.
That isn’t a fault. A file from another app carries the shape of the ride — coordinates and heights — so distance and climb are geometry and come out fine, but speed, duration and hard braking aren’t worked out from it. NavForge’s own exports are the exception: they carry the full recording, so a re-imported NavForge ride shows every number — duration, speeds, braking — exactly as the original did.
Distance is in kilometres, speeds in km/h and climb in metres, whatever you’ve set under Units. That setting changes the map and navigation displays; it doesn’t reach the ride stats yet.
Reading the numbers honestly
Max speed comes from the GPS, not your speedo. It’s the highest single reading in the file, and a satellite glitch under a bridge or between buildings can put a spike in there. If a max speed looks impossible, it probably is — the sensible check is the analytics overlay, where a genuine fast section shows as a run of red rather than one odd point.
Positions are logged every five seconds. That’s plenty for a day’s distance, but it means a tight switchback is drawn as a few straight hops rather than a curve, and the measured distance comes out a touch short on very twisty roads.
Elevation gain is generous by nature. Every climb of more than three metres is added, so rolling country totals up quickly. It’s a fair way to compare two rides against each other; it isn’t a surveyed figure.
The date at the top is when the ride started for a recording — and for a re-imported NavForge export, which carries its original clock. For a GPX from another app it’s the file’s own date on your phone, which is usually when you imported it rather than when it was ridden.
If the screen says it can’t load
Could not load ride data. means the file couldn’t be read or made sense of. That points at a truncated or corrupted file rather than anything you did — most often a recording interrupted by the phone being killed mid-write, or a GPX that isn’t quite valid. The ride will usually still draw on the map if there’s any usable geometry in it, so try Show on map before deleting it.
This screen gives you the totals. The analytics overlay on a recorded ride gives you where those totals came from — which corners were the red ones and where you grabbed a handful of brake.