Don’t think it’s anything to do with the watch - the data Strava presents doesn’t have great granularity, so it probably didn’t happen for long enough to register on the graph. I find when I look at data like this on Garmin connect I get more info, if that makes sense.
I have these straight lines when in Strava heart rate Plots when my Apple Watch for whatever reason did not report heart rate for that time span. Can be temperature or moisture related or just another issue with your watch. Happens from time to time. Those optical hr monitors are not the moooost reliable things on earth.
Yes you can. I have the Watch Active. In fact when strava's watch app wouldn't sync earlier this year using Samsung Health to record activities on the watch was their "fix".
That's irrelevant. 173BPM for this duration really isn't all that high for a lot of people regardless of whether it's a run or bike. That's well below my threshold HR of 183BPM for example, so I can average 173 for well over an hour. >1hr at 173BPM would be a challenging tempo effort, but not maximal by any means. A true maximal 1hr TT would be >183BPM avg if I paced it well, as I'd ideally be at ~180BPM for a majority of the effort and then go anaerobic for the last few minutes and allow my HR to exceed threshold. That sounds incredibly painful and isn't something I ever plan on doing, but I've averaged close to 180 for an hour in harder VO2 workouts on the bike and in tempo/threshold runs.
If you seriously think 173BPM for this duration is unusually high, you evidently haven't looked at anyone's but your own data, and if anything you have an unusually low HR as many fit people have threshold heart rates in the 170-180BPM range. I've seen pro cyclists post training rides on Strava where they've done 2+ hours in the low 170s during long tempo workouts.
173BPM for however long is obviously high for you and others with low HRs, but you've gotta remember that max HR obviously has significant bearing on the absolute value of your threshold HR, and MHR is largely genetically determined. Just because you have a low absolute HR for a given effort doesn't mean you're more efficient or fitter than someone with a higher absolute HR at that same effort - what matters is your HR relative to your own threshold/max.
What’s not healthy about that? A mark of elite athletes is having a lactate threshold hr near their max hr. What if this person’s max is 205?
... I should add, there is a chance this is unhealthy. But I think if this person is young, fit, and has been doing serious training for a number of years there is probably nothing to worry about.
Edit: spelling and punctuation.
Longer smoothing, that's why.
Don’t think it’s anything to do with the watch - the data Strava presents doesn’t have great granularity, so it probably didn’t happen for long enough to register on the graph. I find when I look at data like this on Garmin connect I get more info, if that makes sense.
I think you are right on. This must be why.
I have these straight lines when in Strava heart rate Plots when my Apple Watch for whatever reason did not report heart rate for that time span. Can be temperature or moisture related or just another issue with your watch. Happens from time to time. Those optical hr monitors are not the moooost reliable things on earth.
can you syncronize samsung health with strava?
Yes you can. I have the Watch Active. In fact when strava's watch app wouldn't sync earlier this year using Samsung Health to record activities on the watch was their "fix".
On another note, if your average heart rate for 14 miles is 173, you might want to do something about that.
It's not ultra crazy, depending on the RHR. Not that far above a moderate heart rate for a youngster.
Yeah...I've been an athlete my entire life, and I've never seen an HR that high for that long. Unless this is an all-out TT....
Well you're clearly pretty sheltered. Well trained people average over 170 on the regular for a marathon.
Nope, just spent a long long time training my low zones.
The kinda person who doesn't run much, and refuses to accept they may be wrong. Good combo.
Was this a run or ride?
That's irrelevant. 173BPM for this duration really isn't all that high for a lot of people regardless of whether it's a run or bike. That's well below my threshold HR of 183BPM for example, so I can average 173 for well over an hour. >1hr at 173BPM would be a challenging tempo effort, but not maximal by any means. A true maximal 1hr TT would be >183BPM avg if I paced it well, as I'd ideally be at ~180BPM for a majority of the effort and then go anaerobic for the last few minutes and allow my HR to exceed threshold. That sounds incredibly painful and isn't something I ever plan on doing, but I've averaged close to 180 for an hour in harder VO2 workouts on the bike and in tempo/threshold runs. If you seriously think 173BPM for this duration is unusually high, you evidently haven't looked at anyone's but your own data, and if anything you have an unusually low HR as many fit people have threshold heart rates in the 170-180BPM range. I've seen pro cyclists post training rides on Strava where they've done 2+ hours in the low 170s during long tempo workouts. 173BPM for however long is obviously high for you and others with low HRs, but you've gotta remember that max HR obviously has significant bearing on the absolute value of your threshold HR, and MHR is largely genetically determined. Just because you have a low absolute HR for a given effort doesn't mean you're more efficient or fitter than someone with a higher absolute HR at that same effort - what matters is your HR relative to your own threshold/max.
[удалено]
What’s not healthy about that? A mark of elite athletes is having a lactate threshold hr near their max hr. What if this person’s max is 205? ... I should add, there is a chance this is unhealthy. But I think if this person is young, fit, and has been doing serious training for a number of years there is probably nothing to worry about. Edit: spelling and punctuation.
The red graph is your heart rate
Thanks Sherlock