glyphlabs

Data

How does weekly distance get onto a Garmin watch face, and does Zwift count?

A watch face gets weekly distance from the watch itself: Garmin provides weekly run distance and weekly bike distance as two values in metres, and the face only formats them. Zwift rides count once they have synced to Garmin Connect; we saw that twice on a Forerunner 570 in July 2026.

Calendar week or seven days?

Calendar week. Weekly distance counts from the start of the week on the watch, not over the last seven days; on the Forerunner 570 we measured, the week started on Monday. On 31 July 2026 the watch showed 121.5 km for the week, while Garmin Connect counted 162.1 km over the last seven days. Garmin's API documentation calls the values only "your weekly run distance in meters" and "your weekly bike distance in meters" (Complications API, checked 9 November 2026), so the difference shows only in a comparison like this one. A face shows the number as the watch hands it over and cannot change how the week is counted.

Run, bike or both?

There are two separate values, run and bike, and nothing else. The API has no weekly type for swimming, hiking or total distance. A field that shows both, like Umbra's weekly distance, adds the two: if only one is available it shows that one, and a missing half is never counted as zero. Both values exist from API level 4.2.0, the list of all types is in complications explained.

Do Zwift rides count?

Yes, once the ride has synced to Garmin Connect. On 18 July 2026, after a Zwift session of 85 km had synced, the weekly cycling field on a Forerunner 570 showed 89.4 km for the week. On 31 July 2026 the field showed 121.5 km for the three rides since Monday, two of which came from Zwift and were never recorded on the watch. A function that reads the activity history stored on the watch did not include the synced ride, which is why Umbra uses the complications instead.

Why -- appears briefly after a restart

The face has to subscribe to both values again every time it starts, because subscriptions do not survive a restart. Until the first value arrives, or if a subscription fails, the field shows --. In Umbra a failed subscription affects only that field and is retried at most once a minute, so since version 1.2.1 the value returns without you doing anything. The general causes of dashes are in why a watch face shows --.