Hello, On the 24th, I conducted some tests, first on a practically straight route, and then on a route in the same area with hills and curves. My hypothesis that the Race 2 is incorrectly processing the recorded points was confirmed. The straight route is marked every 500 meters; it was 4.04 km according to the Race 2 and 4.05 km according to the track, measuring almost exactly during the activity. During the activity with curves, the problem returned, subtracting 80 meters from the total: 4.00 km according to the Race 2 and 4.08 km according to the track. I’ve attached some screenshots that I will send to Suunto support: [image: 1777273901039-captura-de-pantalla-2026-04-27-085958.jpg] [image: 1777274020950-captura-de-pantalla-2026-04-27-090132.jpg] I encourage you to conduct these tests and also send them to Suunto (support@suunto.com). It’s the only way they’ll take the issue seriously. If this problem is widely known, I doubt Suunto will sell another Race 2 at its current price. Regards.

I created a support case in Komoot with the GPX and a photo that shows the offset. I should not (this is not my job) but it’s also I can do with my track. I’ll keep this thread updated with their info (if there’s any). I also sent comments in the Suunto App. I made some manual fixes but I’m not sure that an edit of the passing points will make any effect. I also fixed the end at that mountain in Komoot but this is not good at all . I should not edit anything downloaded (in this case I know the track, but that will not happen in a track of a place I have never been). So I’ll test this edited track. I understand I have (at least) fixed the end at the top of the mountain (and the out of the route and the bad climb guidance notifications will not be triggered in that point), but the rest is really a mistery. Perhaps Route Planner is the solution. If you can make the imported GPX tracks have turn-by-turn, that’d be really fantastic.

@cosme.costa Yes, I am also struggling with the settings. It is available on the RaceS, but not on the Vertical 1. I am suprised and confused… So not really a solution so far. Its possible to “enable” backlight on the V1, whatever that means. Always on, adaptive to the sun? But then the battery lifetime is cut in a half(!) Edit: I think I found it. In the general display settings there is a “Standby” option. This enables adaptive backlight for activities - and unfortunately also for Watchface usage. @cosme.costa I now understand what you mean…

@Egika thank you too.

Very Nice!!!

@Francesco-Pagano Maybe a bit sticky, but so comfortabe Looks great, I agree, fits better than original one.

A similar issue has been reported on Reddit: https://www.reddit.com/r/Suunto/s/ON5V0wTTNr with more that one user saying they had this issue.

I am also someone who have been using GPS watches for a decade and half now, starting from Garmin Forerunner 110 in 2011 and having Vertical 2 as my latest watch. I run in Pacific Northwest on mountain trails that are often under a very dense tree cover, under tall coniferous trees such as Dogras Fir, Red Cedar, Western Hemlock, etc. This is an extremely difficult environment for GPS and historically most GPS watches were very inaccurate. For a long time I thought that Suunto Ambit 3 Peak with its massive GPS antenna was perhaps one of the most accurate watches, but the new generation of watches with dual-band GNSS that have been released in the last few years, starting with Garmin Fenix 7 are amazingly accurate in this environment compared to anything we had before. The last generation of Suunto watches with dual-band GPS - Vertical, Race, Race S, Race 2, Vertical 2 - are all very accurate and some of the best in class in terms of GPS accuracy. But in my opinion, still nothing beats the Airoha GNSS chipset that was used in Garming Fenix 7, Forerunner 255, 955, and few other watches a few years ago. I think more recent GPS watches are a bit less accurate even though they may offer better battery efficiency. Here is a comparison of Fenix 7X Sapphire vs. Suunto Race S - on a similar terrain with the same map zoom level. Both of these are are examples of running downhill on a narrow singletrack trail. Both of these show 6 laps on the same loop. You can see that the track produced by Airoha GNSS definitely looks tighter with tracks from laps closer on top of each other. [image: 1776988567192-screenshot-2026-04-23-at-4.55.25-pm.png] [image: 1776987438944-screenshot-2026-04-23-at-4.18.40-pm.png] To be fair, more recent Garmin watches (Fenix 8, Enduro 3) are definitely less accurate than both Suunto watches and earlier Garmin watches. Also, distance wise I think Suunto is a bit more accurate. Garmin had a tendency to shorten the distance by 1-1.5% compared to the distance of the GPS track.

@Nikolai-Simonov said in Live location S+ app: It’s not a bug but feature! you don’t need to re-connect it each time, just take a 5-15 sec to connect. Thanks for all the explanations. The Bluetooth connection to the watch is a bit unclear to me, but I understand the general principle. And I confirm your explanation: even if the app says “waiting for S+ application…”, it will turn green as soon as the activity starts. However, I tried the live tracking again this evening during a run, but unfortunately, it didn’t work very well - version 1.0.16-ext (102) First, I had trouble activating tracking: the watch said it was connected (I had the GPS coordinates on the dedicated screen) and the app indicated a connection with the watch. But I still wasn’t located on the app’s map, either at the start or after a short movement. I had to stop the activity, disconnect and reconnect the app and the watch, and start a new activity to finally be located on the map and see my movement. Several kilometers later, I checked and the watch was disconnected (“DISCONECTED state:99”). I’m not entirely sure, but I think the app still indicated a connection with the watch. I tried disabling the Suunto app on the watch and then re-enabling it, disconnecting from the app and re-enabling it, several times, in various orders, but still without success. I finally gave up on LiveTracking. Last weekend, I also had some issues with version 1.0.13-ext (77) where I experienced a disconnection for a few kilometers, but the connection was restored afterward and the tracking resumed (with a long straight line corresponding to the disconnection). As I work in software development myself, I imagine it can be very difficult to diagnose with just this text information, sorry

@MdzOtt yes, SA is the one not doing it ;). In my case with Karoo Gen 3 I see same avg power with zeros included (gold standard) like you get see with garmin/Strava

@Egika My bad, I have a 9 peak pro and I assumed it was the same for all Suunto Watches ^^

@sartoric ok thanks for the info. I guess it will never be fixed then.

@OutdoorMan said in Minimal watchface (feedback): @dreamer_ I personally just need to have a date in time only mode, because I never remember what date it is. And that’s it Totally agree. Battery icon also means you’,ll never forget charging your device but that is my feeling. I consider the rest of the things totally useless

@Manuel-Extreme There are 3 things Should the the watch always record data even if it can determine the data is incorrect? No Should suunto look into crashes? Yes Am I less concerned with loosing some heart rate data than you? Yes. My original reply is about the first point. But since it is an important point for you I will no longer capture your topic. (Btw, I was not able to reproduce your steps on my race 2, so it could be model specific)

I am on iOS, I let the issue rest, and it appears like the watch was able to get the weather data. However the following evening the same issue happened again. And again in the morning it had synced. I guess I can update what happens this evening and the following morning as well.

@Egika it coulde be average fuel consumtion number that could motivate you to ride more

@2b2bff no, 11 different files that I imported from alltrails.