vo2 max not showing up even after multiple runs and walks.
-
@cosme-costa I’m new to Suunto (8 runs so far, all with a Polar H10 until this mornings). I’ve gotten Vo2 Max estimates, but no Lactate Threshold/Race Prediction numbers yet. I saw some in the forums say you needed to use the watches oHR for it to calculate so I did try that this morning. The oHR was definitely way off to start for the first 15 minutes of the run, and the file ended up saying I had 22 minutes Z4 (53% of the run) and 11 minutes Z5 (27% of the run). So even if the requirement is that the data be from the oHR, I should have had enough for it to generate some sort of estimate (which would have been a wrong estimate since the data was garbage without using a strap for me)
-
There are multiple Vo2Max related topic, so not sure to which to reply, but here we go. I have switched from Vertical to Race and while on Vertical I got a Vo2Max reading immediately after the first run. Now on the Race, after multiple runs (from 1 to 4 hours) with OHR and also with HR belt there is no Vo2Max reading. I have read a lot theories here - but is there a final conclusion how to get a Vo2Max reading?
-
Mystery solved for now. Yesterday myself and my wife went for a run and there was a steep hill where I was already tired and went slowly up. But she started to do uphill intervals. She almost vomited, but she got her first Vo2max reading
My conclusion: to get a Vo2max reading you have to get into very high HR numbers a few times during a run. I was 13 minutes in Z4 during the run and this was still not enough for me to get a reading. -
@timecode Sorry, but I have to disagree. It took me almost two years to get my first VO2max result on my Vertical. The first successful activity was a 65 minutes walk (average 6 km/h) and my HR stayed mostly in Z1 and briefly touched Z2.
Funny thing: the result appeared immediately after the last big SW update and I’ve been getting the results steadily ever since.
A long time ago I asked for exact requirements from Suunto support and there were all kinds of stuff: flawless GPS and HR recording, a specific period of time in Z3 or above etc etc. My activity did not fulfill those requirements which makes me think they have lowered the bar in software.
-
@BrunoH interesting. As far I understand walking shouldn’t produce any Vo2max readings, or? Strangely enough when I had the Vertical it was able to get a Vo2max reading from the very first run, and for each run. Since I have the Race, there’s nothing.
-
I gave a try, had an easy walk yesterday for about 20 min with an average speed of 6.0km/h and 112pbm HR peak , and got my first VO2max estimation (46,2). It was the first time I walked with the smart HR belt, which I use only at the gymn. I will try also with a run …
-
@timecode I think running and walking have always been the supported activities for VO2max. I remember it from my days with S9B.
-
@BrunoH if this is the case, then there something really broken. How come walking is producing Vo2max readings, but not running… makes no sense. I know you don’t know that, I am just thinking out loud.
-
@timecode no vo2max reading here either. I do mainly race biking, I did 3 run exercises, with Suunto hr belt. No vo2max.
-
Honestly, you aren’t missing out on much. The VO2Max value I and all my running friends get regardless of watch or brand is generally pretty useless and the estimated race times based on it equally poor.
I personally find the ‘Effective VO2Max’ value calculated by Runalyze to be far more practically useful.
To give an example, My Race S tells me my VO2Max is 52.3 and it suggests I can currently run a HM in 1:32’50 which is a pace of 4’24/km. Runalyse suggests my ‘effective’ VO2Max is 41.33 and suggests I can currently run a HM in 1:48’20. My last HM (march) was very hilly and 1:47 and my PR in 2023 is 1:40 so I think Runalyse is far closer to reality. I’ll find out on Sunday but I’m not expecting faster than 1:45
