Oura's automatic VO2 max: check the experiment's entry requirements

A software announcement is not the same as a feature appearing in your account. Oura's 20 October update introduces Cardio Effort and automatic VO2 max. For the latter, the useful first question is access: Oura is introducing it through its experimental Labs programme. Before expecting a number, separate the announcement, your eligibility and the data requirements. This guide concerns access to software, not what a health metric means or how to change your exercise.

Three things to know

• Automatic VO2 max is an optional Oura Labs experiment with gradual rollout and regional variation.
• Supported hardware, active membership, platform and language are separate checks.
• Minimum data requirements are not a promised date for your first result.

Check the entry requirements separately

The Oura Labs support page lists Gen3 or later with active membership, on iOS or Android. Gen2 and older are excluded. Labs is currently English-only, and individual features may vary by region. Owning a ring, meeting the hardware requirement and seeing this particular experiment are not interchangeable facts. A product name alone does not settle them.

Oura says the experiment's gradual rollout begins on 20 October. That is a start date, not evidence that every eligible account received it that day. Its help page directs members who cannot see a feature to check the latest app version and the feature requirements. PING has not opened an account to verify the current screen or availability for any particular reader.

Read the data requirement, not a countdown

The Labs instructions give two minimum conditions for a first automatic estimate after enrolment: at least 30 days of Oura data and five completed qualifying workouts, specified as outdoor walks, runs or hikes with GPS location services enabled. This describes the manufacturer's eligibility conditions; it is not a request to undertake exercise to qualify. It also does not say every existing member must collect 30 new days after switching the feature on.

An existing data history and an experiment's start date answer different questions. Do not turn the requirements into a guaranteed result on day 30, or assume that meeting a count proves a result is ready. If something is missing, use the current feature instructions and support route rather than infer a hardware fault from an absent score. No personal data or account has been examined for this article.

Participation remains a choice

Oura describes Labs participation as voluntary, with the option to start or stop testing. Its instructions place available and currently tested features under Oura Labs in the Today-tab menu. Experiments can change, become unavailable or be removed. That makes a feature's experimental status worth retaining in your notes, rather than treating a launch headline as a permanent software entitlement.

Keep a small record of what you checked

A useful proposed check is to record the ring generation, membership state, app version and exact feature name before asking support about missing access. Keep screenshots or account details private when seeking help, and describe the issue without posting a health score publicly. This is a suggested support-preparation habit, not a privacy audit or a claim that PING has verified the experiment's data flows.

For readers in the UK, Nigeria or Kenya, the practical question is the same: what do the current instructions and your actual account establish? These locations are reader examples, not a confirmed country rollout list. Do not infer local access, retail support or delivery from a global announcement. Nor should access to an experiment be confused with proof of accuracy or a reason to alter care.

The modest outcome is a clearer access check, not a promised estimate or a health verdict. Keep optional participation, account eligibility and data requirements distinct. Read more documentation-led technology guides on PING's Gadgets desk.