Apple Watch Series 10 heart rate sensor is a disaster

I am a marathon runner and do not mean that this is not (only) to prove that these memes about runners who always talk about running are absolutely correct: We do it.

I do it because I got there with technology. The Chatgpt training helped me Comfortable half marathons, while the Apple Watch and the iPhone helped me to follow all my training runs and races. Devices and AI made It seems easier to do marathons and I'm not stopping so quickly.

I have to raise this to explain again and againHow much the Apple Watch Series 10 disappointed me. I was thrilled with Apple's latest portable flagship when it comes to battery life and loading speed. These are great upgrades about my Apple Watch SE, which I gave up when the health of the battery fell below the 80% mark.

However, Apple Watch SE never gave me reasons to question its ability to correctly record heart rate data. In the meantime, I have experienced several problems with the Apple Watch Series 10 -heart frequency about which I have written in detail in the past few months.

What usually happens during the training sessions is the following: The heart rate sensor does not show the actual heart rate for a few minutes at the beginning of the session. Sometimes this happens during the entire session, regardless of whether it is a run or a walk. It doesn't matter what the type of exercise is and I'm not the only one who experiences it.

However, the 12 km run from Monday gave me another reason to make me worried about the accuracy of the heart rate sensor of the Apple Watch Series 10.

It was all a regular run in which I had planned to make between 10 km and 15 km with moderate effort. Since it is common with runners, especially those who fear that the Apple Watch Series 10 data will not record 10 data, I checked the wearable shortly after running to see that they do not display the heart rate data. Naturally.

I then decided to continue checking every few minutes to see if it started to record information. Soon I got the statistics in the upper picture. Six minutes after my run, my clock told me that my heart raced with over 150 strokes per minute, despite the slow pace I gave this first kilometer. I had to take a picture and when I fumbled on the phone, it had reached 171 strokes per minute.

I didn't have the feeling that my heart beat so quickly. If you see the statistics, there can be a reason for others to worry. Your heart should not run that early in a current session.

I was excited to see how high it would go and suspected that the heart rate sensor had problems. Shortly after I took this picture, the heart rate settled with around 127 strokes per minute.

A look at the fitness app shows that the massive hike was recorded early in the run as I had experienced.

As you can see, I increasingly increased the effort and then took a short break for a gel after about 6k. My goal for the session was in zones 3 and 4, so between 140 and 165 strokes per minute.

As a long -standing Apple Watch user, I am upset that the heart rate sensor is so common on a flagship device. I appreciate the gaps in the readings, which, incidentally, appeared a few minutes later, as can be seen in the graphic mentioned above. And I don't appreciate the wrong readings.

Could my heart rate have increased before stopping? It is always possible that such readings appear early in a training session. But it is unusual to see such a high heart rate.

For comparative purposes, my heart rate readings for the last marathon I ran look:

Back to the run on Monday, the clock would have preferred to try to save my life and send me to the emergency room after I have given this reading.

The whole thing felt like the Apple Watch Series 10 after a few minutes in which no measured values ​​were shown, guessed a guess with my heart rate. It is as if it has decided to show some random values ​​before you actually perform readings.

Here are the statistics for Monday that I use to explain my next points.

First, I ran much faster during this session without going out, and my heart rate was never as high as in this sixth minute. I was perfectly fine, but I definitely felt the additional effort.

Second, how should I trust this average? If these initial readings are wrong, which I suspect, screw up the average pace and heart rate. This in turn affects the calorie algorithms. In the long term, these statistics have an impact on the health and training trends of the guard registers.

I will also repeat what I said before. If the heart rate does not read during training, how do I know that it takes up enough readings while I'm alone? And if so, how do I know that you are exactly?

I don't want to question the data that comes from the Apple Watch because I will then question his ability to save my life one day.

I could buy a different heart rate sensor that I can use during runs and then compare the measured values ​​with those of my Apple Watch Series 10.

I will still find that I run the latest Watchos 11 beta. Whatever these problems with the heart rate causes, Apple has not fixed it since I started to notice.