Skip to main content
Question

Apple Watch Ultra 3 barometric elevation data is available but ignored by Strava

  • January 25, 2026
  • 2 replies
  • 63 views
S
Forum|alt.badge.img+1

This post is intended to clarify a recurring explanation in this forum that elevation issues with Apple Watch are “Apple’s fault”.

 

I am using an Apple Watch Ultra 3, which records elevation using a barometric altimeter. The elevation data is accurate and consistent across Apple Fitness and third-party apps.

 

Most importantly:

The correct barometric elevation data is present in the exported FIT file, verified via WorkoutDoors.

 

Despite this, Strava consistently discards the elevation data from Apple Watch activities and replaces it with GPS/DEM-based elevation, resulting in significant under-reporting of total ascent.

Example from the same activity:

  • Apple Fitness / WorkoutDoors: ~577 m ascent
  • FIT file (verified): ~577 m ascent
  • Strava after upload: ~480 m ascent

This behavior is consistent across:

  • Direct sync from Apple Health
  • Manual FIT upload
  • Third-party apps (WorkoutDoors, HealthFit, RunGap

Addressing the “Apple’s fault” explanation

The barometric elevation data clearly exists, is consistent, and is exportable. This indicates that the issue is not missing or unusable data from Apple.

Furthermore:

  • Third-party apps are able to read and display Apple Watch barometric elevation correctly
  • The same FIT file contains correct ascent values before upload
  • Strava accepts barometric elevation without modification from Garmin, Suunto and COROS devices

This strongly suggests that the issue is not a limitation of Apple Watch hardware or data availability, but rather a platform-level decision by Strava to ignore or de-prioritize Apple Watch elevation data.

Questions for Strava

  1. Why is Apple Watch barometric elevation treated differently from other barometric devices?
  2. Is this behavior based on legacy assumptions from older Apple Watch models?
  3. Are there plans to update elevation handling now that devices like Apple Watch Ultra 3 provide high-quality barometric data?
  4. If not, can Strava clearly document this limitation for Apple Watch users?

Apple Watch Ultra has become a serious endurance and trail device. At the moment, Strava systematically under-reports ascent for Apple Watch users despite correct sensor data being available and verifiable.

 

An official clarification would be appreciated.

2 replies

C
  • colinmacdon
  • Hub Starter
  • February 1, 2026

My situation is similar (AWU3).   But in my case the watch grossly over estimates the elevation gains.  Typical flat loop around my neighborhood measured with either the garmin Epix or forerunner 970 yields 40-70 meters of gain, with similar descent. AWU3 comes in at 142 meters of gain, with only 29 meters of descent. Not accurate at all.  Strava corrected is in the 40-70 meter range. 
Just because that elevation data is in the FIT file doesn’t mean it is accurate.  The device is writing to that file—who’s to say it’s accurate?   
I believe Strava has a tolerance for when it corrects elevation data, and it has and will correct it if it is not within that range.  I’ve only had the ultra for a short time, but its elevation data is always off, and measures very little descent.  
 

 

S
Forum|alt.badge.img+1

Thank for taking the time to reply. I do not have the same problem as you. My ascent and descent is always very similar. When I run with friends who have Garmin, Coros etc we have similiar elevation on our watches but when uploading to Strava I always loose a lot of elevation compared to them. When the watch is new I’m aware that it self calibrates and you should do that on open surfaces, maybe that could be the problem for you? If it doesn’t get better for you I would ask for a new watch. From the reviews I have read and my own experience fromApple Watch Ultra and series model it measures just as good as any other watch. 

Terms & ConditionsCookie settingsAccessibility statement