Is this pace wrong.

dodgeman

Well-Known Member
Region
USA
City
Macomb, Illinois
So I’ve been using an app called Ride With GPS. It has a stat called pace. I thought this was how long it would take to do a mile. If you are driving 60 miles an hour your pace would be 1 minute. When I go through the help section in the app it seems to confirm this thinking. I posted a pic of a recent ride and I’m just assuming the app is wrong. It seems like my pace should be 4 minutes and some seconds. It has my pace at a speed of over 30 miles per hour. I thought maybe the pace was based on metric but if my math is correct that doesn’t compute either.
2B5943DA-F38D-4785-98B3-E04ADEB3492B.png
 
ya I dont think it means miles but who knows? here is our last ride it was nto a fast one lots of climbing and riding with lots of stops in the city.
Departed:Jun 4, 2022, 9:28 am
Starts in:Johnson City, OR, US
Distance:34.2 mi
Elevation:+ 1656 / - 1608 ft
Max Grade:10.9 %
Avg Grade0.2 %
VAM288 Vm/h
Ascent time01:45:17
Descent time01:18:08
Total Duration:05:52:11
Moving Time:03:07:58
Stopped Time:02:44:13
Calories:1695
Avg Watts:150
Max Speed:23.8 mph
Avg Speed:10.9 mph
Pace:00:10:18
Moving Pace:00:05:30
Max Cadence:198 rpm
Min Cadence:22 rpm
Avg Cadence:69.0 rpm
Max HR:138 bpm
Min HR:70 bpm
Avg HR:99.7 bpm
Heartrate zones:
 
it’s supposed to be average time to complete a mile, but it looks way off. odd.

CC82316D-56E2-439C-BD17-9822649ACD38.jpeg
 
Strangely, it makes sense for my license of RideWithGPS in metric units (only relevant data retained):
1654490777851.png


Moving Pace was 170 seconds per kilometre of my ride. 3600 s / 170 s = 21.17 km/h (Average Speed).
Pace was 302 s per kilometre or 11.92 km/h (Average Gross Speed). All making sense.

Important to mention these data had been recorded by a Wahoo Roam and only transferred to RWGPs post-ride. @dodgeman, @rayray: Do you people actually record your rides with RWGPS? Because @fooferdoggie is using a Garmin.
 
Strangely, it makes sense for my license of RideWithGPS in metric units (only relevant data retained):
View attachment 125368

Moving Pace was 170 seconds per kilometre of my ride. 3600 s / 170 s = 21.17 km/h (Average Speed).
Pace was 302 s per kilometre or 11.92 km/h (Average Gross Speed). All making sense.

Important to mention these data had been recorded by a Wahoo Roam and only transferred to RWGPs post-ride. @dodgeman, @rayray: Do you people actually record your rides with RWGPS? Because @fooferdoggie is using a Garmin.
I use a Wahoo Roam also, and upload from there to RWGPS. I’ve looked at my settings in both apps, and I don’t see anything amiss.
 
I use a Wahoo Roam also, and upload from there to RWGPS. I’ve looked at my settings in both apps, and I don’t see anything amiss.
At least the reported speed makes sense in your case. (Let us leave Pace to runners) :)
 
A recent anecdote!

Instead of riding myself, I was "watching" the Wanoga 2022 (short route) gravel race on the screen of my PC. The route was 357 km (221.9 mi) -- the "full" Wanoga race had been 608 km (377.9 mi).

The winner completed the 357 km race at the average speed of 24.96 km/h (15.51 mph). The ride took him (gross) 14 hours, 17 minutes, and 55 seconds. The second place rider needed some 19 minutes more. The third place guy rode almost one hour more than the winner. (The best female needed over 4.5 hours more than the winner, and she was 19th overall).

Many participants took part in the race as an opportunity for a great adventure. Some of them took as many two night stops on the route. For example, the competitor at the 147th place needed as many as 62 hours and 17 minut to reach the finish line, and there are still people riding! Fancy how low gross average speed she recorded (because only the gross time counts in the race).
 
Last edited:
To me, average speed and pace are the same anyway, as one is calculated from the other.
For me, it is enough to know I need three minutes to ride for a kilometre, and if that's any faster, it's just a bonus :)
 
A recent anecdote!

Instead of riding myself, I was "watching" the Wanoga 2022 (short route) gravel race on the screen of my PC. The route was 357 km (221.9 mi) -- the "full" Wanoga race had been 608 km (377.9 mi).

The winner completed the 357 km race at the average speed of 24.96 km/h (15.51 mph). The ride took him (gross) 14 hours, 17 minutes, and 55 seconds. The second place rider needed some 19 minutes more. The third place guy rode almost one hour more than the winner. (The best female needed over 4.5 hours more than the winner, and she was 19th overall).

Many participants took part in the race as an opportunity for a great adventure. Some of them took as many two night stops on the route. For example, the competitor at the 147th place needed as many as 62 hours and 17 minut to reach the finish line, and there are still people riding! Fancy how low gross average speed she recorded (because only the gross time counts in the race).
But, but, but….what was the pace? 😂. Just for the record, by my calculation the winner was at 2.40384615384615 minutes per km.

By the way, I’d be proud to finish that race at ANY pace. I’m not certain I could handle even half that distance without one or two full days of rest in the middle, and that would be with an ebike.
 
Just for the record, by my calculation the winner was at 2.40384615384615 minutes per km.
Whatever it was, gross average speed of 24-25 km/h in mixed terrain over the distance of 350+ km means the guy must have been a mutant :)

By the way, I’d be proud to finish that race at ANY pace. I’m not certain I could handle even half that distance without one or two full days of rest in the middle, and that would be with an ebike.
I can fancy myself on such a race. If I could take two-night eigth-hour sleep (and a chance to charge batteries in the accommodation), that would make 119 km a day, and I could make it. Pity nobody would let me actually participate with the starting number. I also doubt I would be given the GPX route for the race.
 
Hey @dodgeman,

This is Chad from Ride with GPS, and I saw your comment about Pace being wonky. We fixed this issue in app version 3.0.7 -- updating to the latest version from the App Store should fix that problem for you. Check it out, and shoot us an email at [email protected] if you come across anything else that needs attention. We are always happy to help. Enjoy the ride!
The Apple App Store has 3.0.6.
 
Last edited:
Back