# Power Data captured and displayed in TR is significantly lower

**URL:** <https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282>\
**Category:** TrainerRoad Software\
**Tags:** bug\
**Created:** [February 18, 2026, 6:29pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282 "2026-02-18T18:29:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![candyslokes](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/candyslokes/32/157921_2.png) [@candyslokes](https://www.trainerroad.com/forum/u/candyslokes)\
**Post date:** [February 18, 2026, 6:29pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/1 "2026-02-18T18:29:31Z")

</div>

I’ve never noticed a significant difference in the numbers showed in TR versus what I see while riding in my Garmin or what’s in Training Peaks. But recently what’s been happening with the FTP predictor hasn’t been making sense, but I never questioned it until this am. I was looking at my workouts and noticed a significant discrepancy between what I see in my Garmin device while working out (and in Training Peaks) versus what’s captured in TR. To be thorough, I checked multiple workouts to ensure it wasn’t a one-time bug. I generally do my workouts on the levee system (I live in south FL), which is hundreds of miles of gravel road with nothing to stop you.

Here’s a couple examples:  
Monday 16th - 5 minute V02 Max  
Lap 4:  
TR: NP - 202 \> Avg Power - 133  
Garmin/Training Peaks: NP - 283 \> Avg Power - 283

Lap 7:  
TR: NP - 187 \> Power - 133  
Garmin/Training Peaks: NP - 284 \> Power - 286

Tuesday 17th: 10 minute Sweet Spot  
Lap 4:  
TR: NP - 220 \> Avg Power - 205  
Garmin/Training Peaks: NP - 226 \> Avg Power 230

Lap 7:  
TR: NP - 226 \> Avg Power - 210  
Garmin/Training Peaks: NP - 235 \> Avg Power - 238

Lap 10:  
TR: NP - 230 \> Avg Power - 211  
Garmin/Training Peaks: NP - 240 \> Avg Power - 245

Please advise.

---

<div class="post-metadata">

**Author:** ![HLaB](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/hlab/32/60448_2.png) [@HLaB](https://www.trainerroad.com/forum/u/HLaB)\
**Post date:** [February 18, 2026, 6:46pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/2 "2026-02-18T18:46:14Z")

</div>

Perhaps Garmin is auto pausing but TrainerRoad is also taking the zeros between.

---

<div class="post-metadata">

**Author:** ![candyslokes](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/candyslokes/32/157921_2.png) [@candyslokes](https://www.trainerroad.com/forum/u/candyslokes)\
**Post date:** [February 18, 2026, 7:24pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/3 "2026-02-18T19:24:36Z")

</div>

Auto-pausing isn’t happening because I am constantly looking at my Garmin to see what power I’m doing. I’m riding on Florida’s levee system, so I don’t have to worry about hitting anything because there’s nothing out there to bother me (except maybe gators 🙂 ).

Garmin’s avg power also uses zeros, so they should be fairly close.

---

<div class="post-metadata">

**Author:** ![Helvellyn](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/helvellyn/32/95205_2.png) [@Helvellyn](https://www.trainerroad.com/forum/u/Helvellyn)\
**Post date:** [February 18, 2026, 7:29pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/4 "2026-02-18T19:29:28Z")

</div>

There’s another thread somewhere where the intervals and recoveries seemingly aren’t aligned correctly, which would obviously lead to the efforts reading low and the recoveries reading high. Pretty sure someone from TR is on the case.

Could this be the same issue?

---

<div class="post-metadata">

**Author:** ![candyslokes](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/candyslokes/32/157921_2.png) [@candyslokes](https://www.trainerroad.com/forum/u/candyslokes)\
**Post date:** [February 18, 2026, 7:32pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/5 "2026-02-18T19:32:38Z")

</div>

I did notice there’s significant discrepancy between the intervals and recovery, so much so I didn’t post those because it was so wrong. If you know the thread, can you share it?

---

<div class="post-metadata">

**Author:** ![Helvellyn](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/helvellyn/32/95205_2.png) [@Helvellyn](https://www.trainerroad.com/forum/u/Helvellyn)\
**Post date:** [February 18, 2026, 8:03pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/6 "2026-02-18T20:03:04Z")

</div>

Found it!

> [@TR Lap Bug - Can this affect AI FTP Prediction?](https://www.trainerroad.com/forum/t/tr-lap-bug-can-this-affect-ai-ftp-prediction/111251):
>
> I was absolutely losing my mind after TR dropped my predicted FTP, which is set to update tomorrow, after I nailed the workout that it prescribed today. I went to investigate and saw that it looks like the laps that TrainerRoad are misaligned from the laps that my hammerhead recorded and from what Strava is displaying. This definitely looks like a bug Could this be leading to my predicted FTP decreasing from the value that it was at prior to the ride? I find it hard to imagine that ther…

---

<div class="post-metadata">

**Author:** ![Caro.Gomez-Villafane](https://sea2.discourse-cdn.com/trainerroad/forum/user_avatar/www.trainerroad.com/caro.gomez-villafane/32/129856_2.png) [@Caro.Gomez-Villafane](https://www.trainerroad.com/forum/u/Caro.Gomez-Villafane)\
**Post date:** [February 19, 2026, 12:18pm UTC](https://www.trainerroad.com/forum/t/power-data-captured-and-displayed-in-tr-is-significantly-lower/111282/7 "2026-02-19T12:18:27Z")

</div>

This is a bug we’re currently taking a look at 🙂

As far as affecting your aI FTP Prediction I can’t verify that, but I will let you know if it plays a role.
