@2b2bff I think you are correct. There are a ton of people out there that use older tech. There are the early adopters, the tech insane and those that just do the work with what they have and that means Fenix 5s, 745s and even old Coros watches. That is not to say that I agree that if you are serious about sports you care less about tech. I think it is very individual.

Today I did another test with a different round-trip track. Editing those points of the track in Komoot does not seem to make any effect. The offset is always there. After a while, I went out of the route like 1km and then I returned to the route again and started running back in the route. The autoreverse did not work until a very long time. I started receiving notifications but after skipping many indications. Another little thing: The text when out of the route is extremely small and completely unreadable. This needs a little fix (that icon is just an invented one as an example, and colors and everything should be according to the layout) [image: 1777413648823-out_of_the_route.png]

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.

@Egika thank you too.

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.

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

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.

@2b2bff but it seems it does. At least on the Suunto Run. I saved today’s run to report tomorrow. 2 issues happened. Max heart rate much higher than registered on the HR chart and in the end I did a pause and the connection to the Suunto Chest Straps was lost when I restarted a few seconds later. The maximum HR registered by the chest strap was 154bpm but somehow on the Max HR in the intervals summary many values of 170bpm (these are wrong) appears. Also it can be seen that the HR chart doesn’t end. It was the pause. Unfortunately Suunto seems unable to solve this issue that affects all watches and makes all data contaminated by wrong measures or lack of them. [image: 1777409959845-1000098278.png] [image: 1777409959990-1000098277.png]

@Elipsus said in Core 2?: is it easy to change the battery ? a joke. Sometimes you need to change the o-ring, but again easy

@fondueaufromage Okay, appreciate your information ^_^

@Nandodiver Thanks! I voted!

@rwmastel0 Hi This is a known issue, https://forum.suunto.com/topic/12554/swimming-style-wrong https://forum.suunto.com/topic/14297/swimming-pool-laps-inaccurate/6 but Suunto hasn’t done anything about it

Going to post it here also to see if Suunto makes this issue a priority to them. I saved today’s run to report tomorrow. 2 issues happened. Max heart rate much higher than registered on the HR chart and in the end I did a pause and the connection to the Suunto Chest Straps was lost when I restarted a few seconds later. The maximum HR registered by the chest strap was 154bpm but somehow on the Max HR in the intervals summary many values of 170bpm (these are wrong) appears. Also it can be seen that the HR chart doesn’t end. It was the pause. Unfortunately Suunto seems unable to solve this issue that affects all watches and makes all data contaminated by wrong measures or lack of them. The data sent to other plataforms like Strava or Intervals.icu is correct except for the disconnection in the end. [image: 1777409959845-1000098278.png] [image: 1777409959990-1000098277.png]

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.

@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

@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

@cpinky I understand and sorry for your experience, but I already answered above on that, wait for the next update. Even if this issue for you specifically happens often for majority of users it doesn’t happen or rarely, so it was hard to reproduce. Creating new topic doesn’t help with solving issues, quite the contrary - many topics no one can read, hard to report and use as evidence. Should be one problem - one topic

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

@pavel.samokha Understandable. Will make a repo