GPS tracked runs not populating into the VO2max section of my Whoop

Strain & Activity
1

Since September 25, 2025 none of the 25+ minute GPS tracked runs I’ve done weekly are populating into the VO2 max section of my Whoop app. All the runs are visible & GPS tracked confirmed on the individual days. But when I click on “VO2Max” none of the runs are there. I’ve reached out to Whoop multiple times & they’ve sent me a new sensor last week. I performed the Norwegian 4 x 4 this past Saturday, & on the weekly VO2 max update today (10/28) the run from Saturday isn’t there. Has anyone out there had this issue?

2

Hey @Toddseigler,

Thanks for taking the time to write in.

I understand your concern about your GPS-tracked runs not showing in the VO2 Max section of your WHOOP app since September 25, 2025, despite the runs being visible and GPS tracked on the individual days.

Here are some important points about VO2 Max on WHOOP that might help clarify the situation:

  • WHOOP estimates VO2 Max weekly, typically updating on Tuesdays, and it is a slow-moving metric that changes over weeks and months rather than days.

  • To generate VO2 Max estimates, you need to have logged at least 14 sleeps within the last 21 days.

  • GPS-tracked runs of 15+ minutes improve the accuracy of VO2 Max estimates but are not required for the estimate to appear.

  • The VO2 Max estimate uses a combination of resting heart rate, heart rate variability, exercise patterns, and GPS-tracked performance.

  • Ensure your profile information such as weight and max heart rate is accurate, as this affects the VO2 Max calculation.

  • The runs you do should have “track route” toggled on to be counted for VO2 Max estimation.

  • VO2 Max data can be viewed in My Dashboard or in the Trends section by selecting VO2 Max.

Since you mentioned you have a new sensor and the issue persists, please double-check that you meet the sleep and recovery requirements and that your runs are logged with GPS tracking enabled in the WHOOP app.

If everything seems correct and the issue continues, please reach out to support@whoop.com.

3

The Whoop team is continuing to help me solve this issue. We’ve already performed the items you mentioned as well as other steps with no positive result. Whoop reached out to me this morning & stated “Our team has now submitted a detailed bug report to our engineering group for further analysis so they can identify and resolve the problem as quickly as possible. At this stage, we kindly ask for your patience while we await their updates.”

I posted in this forum hoping someone else had experienced this issue to possibly gather intel from a fellow whoop member. This is obviously a backend processing issue for GPS data integration. Hopefully this will be resolved soon.