FW 9.33: Running VO2max value vs Garmin Connect Web

If I compare the running VO2max value on my watch with the value in Garmin Connect Web, I see a significant difference.
The value on my Epix is approximately 42.75

And the value in Garmin Connect Web is 42.34 (using Excel CSV export):

This means a difference of 0.5.
My expectations for VO2mx is to have the same values on both sides. Can some explain me the difference or is this a bug?
Thanks!

  • I cannot answer your question but I don’t believe that - even if measured under laboratory conditions - a VO2 estimate can credibly purport to be accurate to two decimal places. No matter how clever the algorithm, your watch is merely measuring proxy values and attempting to extrapolate from them. I am sure this is why both GC and your watch round the values to the nearest whole integer. If I had to guess as to why the fractional data was retained at all, I’d suspect it was for dealing with borderline cases so Garmin can say at the end of your run that your VO2 is trending up or down, even when the movement is too small to result in a whole integer change. You get some of the advantages of being given a directional indicator of your fitness without the watch or GC pretending to measure VO2 to an improbable level of accuracy. As long as GC and your watch display the same VO2 value, that’s about all you can reasonably expect.

  • I totally agree what you are saying, but with the last sentence you hit the point why I was writing this post. For two weeks my VO2max was climbing and GC and my watch displayed different values for some days. My watch had a value of 42 whereas GC displayed 43.
    I actually believe that my watch does the VO2nax calculations and GC transmits this value to GC for each actiivity. Afterwards I can see the same value in GC. Now it seems to me that GC is calculating the VO2max itself and this leads to a slightly different result. Can you confirm my assumption?

  • The issue crops up from time to time on the forums. The general consensus seems to be that the numbers eventually sync up so there may be a timing or similar issue. It has never happened to me (that I have noticed) and I agree that superficially it seems a little untidy. I think any further speculation by me would be well into wild guess territory!

  • I've had this continue to happen to me on my Epix 2 even after 3-5 months of use. I had assumed it was just a rounding error where my watch shows 52 and my phone shows 53 but the real number was 52.5. But... I had never exported and checked what the underlying number was.

    You are showing that the watch and phone number are actually different which is not what I was expecting.

    I would suggest raising it as a bug to Garmin.

  • Hello TheSalmander,
    do you know how is the procedure to raise a bug to Garmin?
    Thanks!