VO2 max Uth-Sørensen calculator

This capability takes hr_max and hr_rest in beats per minute, validates that both are positive finite values with maximum strictly above rest, multiplies fifteen point three by their ratio, and returns structured JSON with the ratio, estimated VO2 max in millilitres per kilogram per minute, and the formula string. The path is pure arithmetic with no network and no random seed, so homework checkers, training apps, and prepaid API clients get identical results every time. Invalid inputs raise a clear invalid_input error and are not charged.

What the Uth–Sørensen heart-rate ratio method measures and which inputs you need

VO2 max is the highest rate at which your body can take up and use oxygen during intense exercise, usually expressed in millilitres of oxygen per kilogram of body mass per minute. Laboratory protocols measure it with gas exchange on a treadmill or bike, but many coaches still need a practical estimate from heart rates alone. The Uth–Sørensen–Overgaard–Pedersen formula maps the ratio of maximum heart rate to resting heart rate into estimated VO2 max with a single scaling constant: VO2 max equals fifteen point three times HRmax over HRrest. Send required hr_max as a positive finite bpm value; aliases hrmax, max_hr, maximum_heart_rate, and hrm are accepted. Send required hr_rest as a positive finite resting bpm; aliases hrrest, rest_hr, resting_heart_rate, and rhr are accepted. Maximum must be strictly greater than rest—equal or inverted rates cannot describe a valid ratio trial and fail with invalid_input. The engine echoes both inputs, reports hr_ratio as HRmax divided by HRrest, and returns vo2max_ml_kg_min with unit_vo2max set to ml/kg/min. Identical inputs always yield identical JSON because the algorithm never touches the network, a model, a clock, or a random generator. Missing fields, non-finite values, non-positive bpm, unrealistic rates above the isolate ceiling, and inverted pairs all fail with invalid_input and are not charged.

Reading the response fields and common measurement pitfalls

Use a true resting pulse taken after several minutes of quiet sitting, ideally morning, not a mid-day average while walking. HRmax should be a measured peak from a maximal effort test when possible; age-predicted formulas such as two hundred twenty minus age are popular substitutes but add their own bias, and this calculator does not invent HRmax from age. Remember that the estimate assumes honest inputs and a healthy cardiovascular response—medications, illness, heat, caffeine, and poor sensor contact all bias heart rates, and this tool does not correct for environment. On success the response echoes hr_max and hr_rest after normalisation, hr_ratio as the dimensionless maximum-to-rest quotient, and vo2max_ml_kg_min as the estimated maximal oxygen uptake. The unit_vo2max field is always ml/kg/min so UIs can label the number without hard-coding strings. The formula field restates VO2 max equals fifteen point three times HRmax over HRrest, method is always uth_sorensen_hr_ratio, and uth_factor echoes the constant fifteen point three so downstream code can branch without sniffing shapes. Non-positive or inverted rates raise a clear invalid_input message. Do not confuse this endpoint with Cooper twelve-minute distance tests, Rockport one-mile walk equations, Karvonen training zones, or laboratory VO2 peak: those are different intents and live in separate products.

API usage, pricing, coaching workflows, and practical limits

Call the free in-browser VO2 max Uth–Sørensen calculator for PE classes, club fitness days, and quick athlete checks without building a spreadsheet of constants. Keep expectations clinical: this is an educational and planning field estimate, not a diagnostic medical device, and athletes with health conditions should follow professional advice rather than any single formula alone. Send a JSON body with required hr_max and hr_rest in beats per minute. Use the prepaid API when a coaching SaaS, sports-science notebook, school LMS, or training log needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with your own resting-pulse protocol and an honest HRmax source, then store vo2max_ml_kg_min alongside date and conditions for longitudinal charts. Prefer measured peak heart rate from a maximal field or lab effort; if your UI only has age-predicted HRmax, compute that client-side and pass the result as hr_max so the engine stays a pure ratio transform. Authors shipping SDKs can map vo2max_ml_kg_min directly into dashboards and export CSV columns labeled heart-rate ratio and estimated VO2 max—the same numbers coaches compute by hand after recording rest and max bpm.