← Back to Learn

Field note 14 · Reading sleep totals

Time Asleep, Time in Bed and the Night Window

Three numbers can describe the same night without meaning the same thing. Compare their coverage before deciding that a missing hour is a mistake.

Ask what the total includes

You open two sleep screens. One says seven hours, another says eight, and the first and last timestamps span eight and a half. Before choosing which screen is right, name what each measures. A span between endpoints, a total of asleep categories and time in bed can all answer different questions.

Our review of Nutrinaut’s sleep-data handling found an additional trap: two totals may match because the application calculates them from the same inputs. Agreement can confirm arithmetic without providing a second observation. This article turns that finding into a practical reading method. Every numerical example here is synthetic; none is an individual sleep history.

The night window

510 minutes

The elapsed span between the first and last relevant endpoints. It may contain awake periods, unclassified gaps or separate episodes.

Time asleep

420 minutes

The sum of compatible asleep categories. Here: 270 core + 60 deep + 90 REM. Sleep without a specific stage also belongs in an asleep total.

Time in bed

480 minutes

A separate category or summary. Check its source definition and interval; do not add it to the sleep stages.

For an interval crossing midnight or a clock change, calculate elapsed time from complete timestamps with their offsets. The difference between printed clock labels may give another answer. One Night, Two Dates walks through that check.

Runs in your browser · No upload

Compare the coverage

Start with the invented example above, then enter totals you have checked. The blocks show amounts, not the chronological order of sleep stages. This page does not fill missing minutes or correct a device.

Window and separate in-bed total

First to last endpoint; maximum 48 hours for this comparison.

Kept separate. Enter zero only for a recorded zero.

Category durations

Use minutes from the same interval. Enter zero for a category recorded as zero. If a value is missing, do not replace it with zero; use the example or check the source first.

What have you checked?

Example interpretation

420 minutes of asleep categories + 30 minutes explicitly awake = 450 classified minutes. The 510-minute window leaves 60 minutes unclassified. The separate 480-minute in-bed value is not added.

An unclassified minute is not an awake minute

In the example, the categories account for 450 of 510 minutes. The remaining 60 minutes are unclassified in the supplied data. Calling them awake would introduce an observation that was never entered. Calling them asleep would do the same.

There is another distinction: “asleep, stage unspecified” means the record identifies sleep without classifying its stage. It is not an uncovered gap. If you enter 20 unspecified minutes, asleep categories rise to 440 and uncovered time falls to 40, assuming all categories cover distinct parts of the same window.

The separate in-bed row matters. Apple’s HealthKit documentation describes in-bed samples that overlap detailed sleep samples. It also notes that Apple Watch awake samples occur between sleep samples, so detailed categories may not cover the beginning or end of an in-bed interval. An in-bed total minus an awake total therefore needs a definition check before being treated as asleep time. Apple’s category documentation.

A category is also not proof of sensing accuracy. The visual checks arithmetic and stated coverage. It cannot establish what happened during a gap, how well a device classified a stage, or whether a person slept well.

Matching numbers can share one calculation

Suppose core, deep and REM total 420 minutes, and another field displays seven hours. Dividing the first sum by 60 produces the second number exactly. Their agreement is expected if both come from the same calculation. It does not give two independent confirmations of the night.

In the inspected Nutrinaut source, one sleep-data path groups unspecified asleep duration with core, while another provider path maps categories differently. A label alone cannot tell you whether two summaries are comparable. Historical app versions and data sources may differ, so inspect the original category before comparing exported fields.

Try the shared-formula example in the Data Forensics Lab to see how one changed input moves several outputs together. A percentage calculated from sleep and in-bed totals inherits the definitions of both; it is not a separate measurement of sleep quality.

Two useful warning examples

More categories than window: a 480-minute window with 300 core, 90 deep, 90 REM and 30 awake totals 510 minutes. Those categories cannot all occupy separate minutes of that window. Check overlap, units, interval selection and sources before interpreting the excess. The calculator withholds a coverage breakdown rather than drawing a negative gap.

Several sources: a watch and another app might each contribute records for the same interval. Adding all their category durations can count some time twice. Totals alone cannot identify the overlapping minutes or decide which source to retain. Return to timestamped records; do not choose the smaller total simply because it looks plausible.

A five-step check for your own screen

  1. Name the interval. Preserve its endpoints and offsets. Establish whether it describes one episode or a wider reporting window.
  2. Name each category. Separate asleep, unspecified asleep, awake and in bed. Keep a missing field distinct from a recorded zero.
  3. Check coverage. Confirm that the durations belong to the same interval and do not overlap before subtracting them from the window.
  4. Trace the calculation. Ask whether a second total was measured separately or calculated from the first set of fields.
  5. Keep unresolved time visible. Annotate the gap or definition mismatch before comparing nights. Do not silently turn it into extra sleep or wakefulness.

Once the definition is stable, compare like with like across nights. If the definition changes, mark that break in the diary. A consistent label is useful only when its meaning stays consistent.

Sources and method

Method 1.0 · checked 15 October 2026. The comparison adds the four entered asleep categories and explicit awake minutes. It subtracts their sum from the window only when the selected source, coverage and non-overlap conditions permit that interpretation. In-bed remains separate. No efficiency or health score is produced. Inputs stay in this browser; the comparison uses no account storage or model service.

The Nutrinaut source review informed the distinction between original categories and derived summaries. It is not proof that every historical record used the same application version, or independent validation of a wearable. Public examples are invented and contain no private records.

  1. Apple: HealthKit sleep-analysis categories, overlap and coverage.
  2. Nutrinaut Connections & Data Guide.
  3. Nutrinaut Tools methodology and sources.