Running Ground Contact Time

Ground contact time describes how long your foot stays on the ground while running. Apple Watch displays it in milliseconds; 320 ms means about a third of a second. A stored reading is an estimate of contact duration, not a timestamp for every footfall. Apple's HealthKit reference defines discrete time samples collected during outdoor runs on supported watches.

The July–September 2026 example contains 5,710 readings from one source group across 13 runs. These are observed values, not population reference ranges or training targets.

The histogram weights every stored reading equally, so longer or more densely recorded runs contribute more. The second panel gives each paired run one point. All extremes remain visible; an outlier flag is a reason to inspect its timestamps and context, rather than proof of an error or a clinical abnormality.

The median positive gap between sample starts in this quarter was 5.13 seconds. This calculation includes gaps between runs; the mean would be dominated by those gaps. All quarter readings were point records with equal start and end timestamps. That is the stored shape, not proof that the sensors only operated once every 5.13 seconds.

Earlier months contained longer interval records. Apple documents that workout samples may be condensed or coalesced, so a change in sample counts or interval length is not automatically a change in training volume. Recording cadence is also different from running cadence in steps per minute.

Contact time increased by a median 13 ms from the first to last elapsed-time third across 13 runs. The calculation compares medians of point readings in the first and last thirds of elapsed workout time, with at least five readings per third. Pace, terrain and pauses were not controlled. It cannot establish fatigue, fitness improvement or form breakdown.

Every quarter reading overlapped a recorded workout; none overlapped a recorded asleep interval. The example therefore supports comparisons within and between runs. A day without readings means no stored observation of this type, rather than a physiological zero.

Compare similar running conditions before comparing the number. An easy jog and a faster effort can produce different contact times without either indicating a problem. There is no universal Apple Health cutoff that diagnoses poor form, overstriding or injury from this measurement alone. This type also does not supply separate left and right contact times, so it cannot establish contact-time asymmetry.

In the example 13 paired runs, faster run-median speed was associated with shorter run-median contact time (Spearman −0.71). That is a descriptive association between workouts, not a controlled test of economy. Stride length, power and heart rate describe other aspects of the same run; none establishes a causal benefit from deliberately shortening contact time.

HKQuantityTypeIdentifierRunningGroundContactTime is a discrete quantity type, introduced in iOS 16/watchOS 9. Use averages, distributions or matched comparisons rather than summing readings. Automatic outdoor-running support is documented by Apple; the HealthKit reference names Apple Watch SE and Series 6 or later.

Raw quantity samples and workout-linked series are kept separate. This quarter contains 5,710 raw readings and 5,710 series points for this type; these counts are representations, not additional independent measurements to pool together. Source revision groups are provenance, not proof of a permanent device identity.

The research uses an October 2025–September 2026 extract with a July–September focus in America/Los_Angeles. Workout relationships use fully contained readings, the same source group and uniquely overlapping running workouts, with one median per run. Sleep and general workout context use timestamp overlap rather than explicit HealthKit associations. Context beginning before the extract boundary may be missing. The private executed notebook retains all eleven analysis facets, source changes, outlier checks and unsupported questions. Public figures omit dates, source names, identifiers and routes.