the timescale is clearly wrong. i like to compare the strongest-one-hour-power for various rides. now i don't know if that's what i'm seeing or not!

this is a 2 hour and 6 minute ride. the time is definitely correct, matches reality, the cycling app the data came from, etc. the timescale on the power curve (for this ride, not for all time) clearly goes to more like 3.5 hours. i see a similar ratio on many, but not all rides. anyone else?n



no love on google. https://www.google.com/search?q=stra...client=gws-wiz

Yesterday, I did a ride with 2:50:34 moving, but the elapsed time was almost 4 hours. I have attached a screen grab for reference. This got me curious, so I went and verified a few other rides where I knew there was a noticeable difference between the moving time and elapsed time, and those power curves also were based on elapsed time. It appears that the power curve chart is based on the elapsed time.

yes - it’s definitely based on elapsed time, as it probably should be. that’s not what’s causing the oddity in my rides though, most have only a few minutes of stopped time. the example above is 2:08 in calendar/clock minutes start to end!

Interesting. All of mine (at least the 20 or so I just spot checked from the last 6 weeks) are using the correct elapsed time.

so strange. i have to go back very far to find a correct one, but it looks like all the ones uploaded from the cadence cycling app (vs different apps i used to use) are all displayed with the wrong x axis.

what's very interesting is that the numbers seem to be correct; e.g. the one hour average matches what i saw on the bike after the first (usually strongest) hour of the ride. mystifying.

Garmin 1030 recordings.
Last week, a ride was 1:46 ride time, 2:06 total time.
The power curve showed 2:06.

In Golden Cheetah, the line extends to 2:06 also. Looks like stopped times are factored in, which makes sense.

That's why my over 1 hour chart line is so low. Rides have at least some stopped time, and downhill coasting too. An interesting experiment would be to do a 2 hour flat ride, trying for a consistent pace with no coasting. Those kind of routes are very hard to find around here, though. A flatland 4-sides-of-a-square repeated loop would be annoying! I want a destination, and stuff to see along the way.

i hear you! my favorite routes have sometimes become favorites because they have almost no stopping. i think i've managed 2 hours without a single stop, taking some liberties with unoccupied four-way-stop intersections. most of my rides in the 1-3 hour range end up with perhaps 5 minutes of stops max, which doesn't skew the curve much.

You’ve got me thinking...


The start/end point is 2.5km from house, and it is flat AF until roughly the 70km mark, along train tracks and canals, definitely not a boring 4-corners big square crit. In reality that is a 2:30:00 to 2:35:00 TT. I might just do it. For science, and all.

been emailing strava support about this. it's a bit of a slow conversation as they take a few days to reply between emails... but there's clearly something wrong. they've manually "reset the power curve" for one activity, and it's fixed with the correct x axis duration on the power curve. today's ride is also correct. every other ride for the past months is still wrong though. wierd.

doesn’t seem like anyone else but me has this issue here, but here’s the latest:

here is the latest from strava after a few weeks of emailing back and forth.

it’s basically every ride that i’ve synced to strava from the cadence app on one particular phone for the last several months. they are able to manually “reset” the curve for a specific activity, which fixes it, but it looks like there’s no explanation yet for why they get like they from this particular combo of app/device.

all the data in the app is correct, including averaged and weighted average power, and exported TCX or FIT files from the app also show correctly in other platforms!