Swimming Stroke Count

This quantity adds up recorded swimming strokes over an interval. It uses count units and cumulative aggregation, so a large sample can reflect more swimming rather than a faster stroke rate. Apple defines the quantity without establishing a universal target count or a guaranteed per-lap recording interval.

The example data contained 51 stroke-count intervals on one May recording day, all from one source group. Counts ranged from 7 to 17 per interval, with a median of 11 and a raw total of 572. All were finite, positive integers; duplicate UUID and identical-content checks found no candidates. These values describe this recording, not beginner, advanced or elite technique thresholds.

The figure shows changing counts beside interval durations. A higher count does not by itself indicate fatigue: interval duration, stroke style, swimming speed and rest can also change. The observed start gaps are the cadence of stored intervals, not a measurement of how often the wrist sensor sampled movement.

Each stroke interval had one exact same-source timestamp match to a distance interval of approximately 22.86 m. Among those positive pairs, distance divided by recorded strokes ranged from 1.34 to 3.27 m per stroke, with a median of 2.08. Matching was restricted to unique exact intervals; no ambiguous interval pairs required exclusion.

That ratio is useful for exploring the data, but it is not a validated efficiency score. Comparisons should keep distance, timing, stroke convention, stroke style, pool length and source consistent. Fewer strokes can accompany a longer glide or slower swimming, so count alone cannot establish improvement.

The overlapping swim workout retained a length setting of 22.86 m, but no lap events or detailed statistics were exported. The analysis therefore did not assign lap membership or calculate SWOLF. A same-time distance match supplies a denominator for a descriptive ratio; it does not replace verified lap timing.

Stroke-style metadata was present on all 51 count samples, with the same raw code throughout. Apple's documented stroke-style enumeration includes unknown and mixed values as well as individual strokes and kickboard. Avoid invented numeric labels: retain the original value and decode against the actual enumeration. Apple documents stroke-style values and the metadata's lap-event scope.

The maximum gap after a stored interval was 109.55 seconds. Two adjacent gaps were slightly negative by less than 0.0002 seconds, consistent with a boundary precision issue rather than evidence of simultaneous swimming. Long gaps may reflect rest or missing recording; neither cause is established by the timestamps alone.

Only one recording day occurred in the October 2025–September 2026 research window, and there were no observations in the July–September focus window. Habitual cadence, fatigue trends and training adaptation are unavailable. Heart rate or energy can add workout context when coverage is aligned, but stroke count does not determine either quantity.

Keep interval counts separate from total-workout counts and preserve the source's counting convention. Summing overlapping streams can double-count activity. Missing records are not zero-stroke swimming. Apple Watch's swimming summary can provide sets, rests and stroke information, but those user-interface features do not guarantee that every exported quantity row carries lap details. Apple's swim guide describes the workout summaries.