Transfers

How do Hammerhead Karoo rides get to Garmin Connect?

A Hammerhead Karoo does not write rides to Garmin Connect directly, so a ride gets there only as a file that something else uploads. Nabe reads your Karoo rides through Hammerhead’s official interface and uploads each ride’s FIT file to Garmin Connect, if you choose with the identity of your own watch, so that Garmin lists the ride as a recording of that watch.

Which connections does Hammerhead offer itself?

Ten linked services, and Garmin Connect is not one of them. Hammerhead’s page Dashboard - Linking Third-Party Accounts, read on 15 November 2026, names AXS, Intervals.icu, Komoot, Ride with GPS, Sentiero, Strava, Suunto, TrainerRoad, TrainingPeaks and Xert, and says rides can also go out to these services automatically. The page Karoo OS - Auto Upload to Third-Party websites, read the same day, lists where a Karoo uploads finished rides automatically: Strava, Suunto, AXS Web, TrainerRoad, TrainingPeaks, Ride With GPS, Komoot and Xert. Garmin appears on neither page. The detour through Strava does not lead to Garmin Connect either, as explained in why Strava activities do not show up in Garmin Connect. For other apps, Hammerhead names a public API on its page Dashboard - Training Metrics, read on 15 November 2026.

How does Nabe read rides from the Karoo?

Through Hammerhead’s official interface, after you sign in to Hammerhead once from Nabe’s Connections. From then on reads is on for Hammerhead, and Nabe picks up each new ride from that moment; older rides go only through Transfer older activities, never all at once when you connect. With writes on for Garmin Connect, each new ride goes there, and Nabe uploads it through the session of your Garmin sign-in. Why that sign-in fails in some sync apps, and how Nabe signs in, is in why the Garmin Connect login fails in sync apps. Which other apps name Garmin Connect as a destination is in RunGap alternatives for Garmin Connect.

What does Nabe take from the FIT file?

Start time, duration and distance. The list Hammerhead returns gives values Nabe shows only until the ride’s FIT file has loaded; after that, the values from the file’s session replace them. Nabe loads the files one after another in the background, at least 2 seconds apart, and if Hammerhead answers with 429 (too many requests), Nabe waits as long as Hammerhead’s answer asks before it continues.

The file Nabe uploads to Garmin Connect is the ride as the Karoo recorded it. With your watch’s identity switched on, Nabe changes only manufacturer, product, serial number and software version in the File ID and Device Info of the file; on our reference ride from a Wahoo ELEMNT ROAM that was 14 bytes in these fields plus the two bytes of the checksum at the end of the file, together 16 bytes out of 227’041. Every other value stays as recorded, as described in what changes in a FIT file when Nabe sends it to Garmin.

What happens to a ride without a file?

It stays in Nabe’s list with the values from Hammerhead’s list and does not go to Garmin Connect, because there is nothing to upload. If Hammerhead answers the request for a ride’s file with 404, Nabe marks the ride for Garmin as skipped with the reason “no file at Hammerhead”, and the other rides carry on. Whether Hammerhead’s interface returns a file for every ride, we have not seen on a real account: this path is tested only with simulated Hammerhead responses. Wahoo has the same case, with numbers from our own account, in how to sync Wahoo rides to Garmin Connect.

How does a ride you also recorded on your Garmin watch not count twice?

Nabe checks Garmin Connect for the same ride before every upload and skips the upload if Garmin already has it. Two recordings count as the same ride when the sport is identical, they start within ±120 seconds of each other, the duration differs by no more than 2 % and the distance by no more than 2 % or 500 m, whichever is larger. For a Karoo ride the check uses the values from its FIT file. In Nabe’s statistics, a Garmin entry within ±120 seconds of a Karoo ride whose file has not loaded yet is left out until the file is there, so the ride does not appear twice there either. Why the rule compares ranges and not rounded values is in how to avoid duplicate rides.

When does Garmin count the ride for Training Effect and training load?

When Garmin treats it as a recording of a Garmin device, or when it comes from a platform Garmin lists. Garmin’s page Can Third‑Party Activities Impact My Garmin Training Metrics?, read on 13 October 2026, lists Concept2, Peloton, Rouvy, SYSTM, TrainerRoad, Wahoo and Zwift; Hammerhead is not on it. Why a ride from elsewhere does not count is in why an uploaded ride does not count toward Training Status.

With your watch’s identity switched on, Nabe uploads the ride as a recording of your watch. What Garmin then calculates we measured on a Wahoo ride: an aerobic Training Effect of 4.3, an anaerobic Training Effect of 2.3 and a training load of 206, read on 30 October 2026; whether this training load went into Training Status and acute load on the watch, we did not measure. For Hammerhead the same path is tested only with simulated responses, and we have not measured a real Karoo ride with a watch’s identity. After the upload your watch has to sync, an Edge twice, as described in how an Edge and a watch share training load. Garmin’s terms of use do not provide for the watch’s identity, which is why the switch is off until you turn it on.