Resting heart rate is not one measurement

Measurement-definition audit · Oura and Garmin · Checked November 21, 2026

Two resting-heart-rate numbers can disagree before either sensor makes a mistake. “Lowest during the night,” “nightly average” and “lowest 30-minute average during a day” select and summarize data differently. Printing bpm beside all three does not make them interchangeable.

Before explaining a sudden change as improved fitness or poor recovery, check whether the measurement changed. This is especially important when switching devices, joining exports or reading a dashboard that shortens every field name to RHR. The abbreviation is too small to carry the method by itself.

Four documented fields

Public definitions, not a reconstruction of proprietary algorithms
FieldDocumented summaryWindow
Oura Average RHRAverage resting heart rate captured during the nightNight
Oura Lowest RHRLowest resting heart rate captured during the nightNight
Garmin daily RHRLowest 30-minute average24-hour period
Garmin seven-day average RHRAverage of daily resting values across the last seven days, on devices offering itRolling seven days, not a calendar-week reset

Oura's help page identifies both nighttime fields and says RHR values are captured every ten minutes. Garmin's calculation guide defines the daily and rolling fields and notes that missing overnight wear can reduce estimate accuracy. Those are documented definitions. The pages do not disclose every sampling, filtering, weighting or missing-data decision needed to reproduce the commercial output.

We therefore leave those implementation details unknown in the download. We do not assume that “average” always means an unweighted mean of every visible point, or that a displayed graph contains all data used internally.

One invented trace, three correct summaries

To isolate the arithmetic, imagine six consecutive ten-minute bins. Their average heart rates are 50, 55, 60, 65, 60 and 58 bpm. All bins are complete and equally long. This is a synthetic one-hour teaching trace, not a person's night and not an emulation of Oura or Garmin.

Different rules applied to the same invented, complete data
Rule in this exampleCalculationResult
Lowest ten-minute binMinimum of the six bin means50 bpm
Lowest aligned 30-minute meanMinimum of four consecutive three-bin means55 bpm
Whole-hour mean(50 + 55 + 60 + 65 + 60 + 58) ÷ 658 bpm

Nothing about the underlying trace improved between those rows. The difference is entirely the calculation. The 30-minute windows here start only at our ten-minute bin boundaries; a real device may consider other alignments, data or exclusions. Calling 55 a reproduced Garmin result would go beyond this example.

Now consider a separate invented week of daily resting values: 57, 55, 56, 54, 56, 55 and 59 bpm. Their mean is 56 bpm, while the latest day is 59 bpm. A daily tile and a seven-day tile can therefore differ by 3 bpm without contradicting one another. Again, this is transparent arithmetic, not a diagnosis or a claim about a particular app's missing-data behavior.

A device change can create a break in the series

Imagine exporting a month of nightly averages, then appending a new device's daily low-window values under the same column name. The resulting chart may look continuous, but its measurement definition is not. A before-and-after comparison now mixes a possible physiological change with a change in method.

Keep the source and field name with every value. Mark the switch date. If you have an overlapping period, compare like-for-like fields where they exist and preserve the wear conditions. An overlap can describe agreement in that setup; it does not automatically establish which device is clinically accurate or justify a universal correction offset.

Subtracting a fixed number to make the lines meet is especially tempting. It also assumes that the difference stays constant across nights and activity patterns. These documentation pages do not establish that assumption. A visible discontinuity with an explanation is more honest than a smooth line built on an untested adjustment.

What to check when the number surprises you

  1. Read the complete label. Is it a current heart rate, nightly average, nightly low, daily RHR or multiday average?
  2. Check the period and date. Confirm whether the two views refer to the same completed window.
  3. Check coverage and source. Overnight nonwear, a changed source or an incomplete record can complicate comparison.
  4. Check the documentation for that feature and version. Keep unspecified processing rules unspecified.
  5. Only then consider what the trend might mean in your own context. A calculation mismatch should not become a confident health explanation.

This guide does not supply a “good” resting heart rate, a training clearance or a threshold for illness. If the reading accompanies symptoms or raises a health concern, seek appropriate medical advice rather than using a source-definition audit to dismiss it.

Data and limits

We manually checked the two manufacturers' public definitions on November 21, 2026. The CSV and JSON contain the four fields, their sources, the complete synthetic sequences and calculation assumptions. No device was worn or tested for this article. It addresses definition mismatch, which is separate from sensor accuracy.

For a related example involving beat-to-beat intervals rather than bpm, see why HRV numbers are not interchangeable. Publisher disclosure: we make Vora, which combines proactive AI with wearable, nutrition and workout context. Keeping a measurement's meaning attached is part of making that context useful. Explore the product; the reference requires no account. Corrections: support@askvora.com.

Frequently Asked Questions

Are Oura average RHR and Garmin daily RHR defined identically?

No. Oura describes average RHR captured during the night; Garmin describes the lowest 30-minute average in a 24-hour period.

Does the synthetic example reproduce either device algorithm?

No. It applies transparent rules to invented ten-minute bins. Proprietary filtering, weighting and other implementation details remain unspecified.

Should I add a fixed offset after changing devices?

This reference does not establish a calibration offset. Preserve the source and field definition, mark the change and compare like-for-like information where available.

Sources & References

  1. Oura Resting Heart Rate
  2. Garmin Resting Heart Rate calculation

All research discussed in this article is summarized in our own words. We link to original sources for full access. This content is for informational purposes and does not constitute medical advice.

WearablesEvidenceMeasurement

Experience it yourself

AI-powered workouts, photo nutrition logging, HRV recovery tracking, voice coaching, and more - all free to start.

Related Articles

Wearables

Your stress tracker cannot tell you how you feel

Oura, Garmin and Google Health describe different stress-related features. Our source map and observation sheet separate readings, feelings and causes.

Read more
Wearables

Five nights do not make a seven-night sleep average

A complete synthetic example shows how two missing nights reverse a weekly sleep comparison. Download the inputs, formulas and reporting checklist.

Read more
Wearables

Your watch VO₂ max is an estimate, not a verdict on your future

A version-specific validation study, method comparison and synthetic worksheet explain bias, individual error and why an upward trend needs context.

Read more