If I’m reading the tiny, blurry print right, in the last screen shot, you have more time at higher power zones than in the TR shot before it. Also, somehow, you have 33 seconds of coasting in the TR shot. That makes me wonder if there isn’t something hinky in the data that affects TR.
In the TR shot, you have 2:22 of power and 0:33 of coasting; in the last shot, you have 3 minutes of power and no coasting. So, yeah, I’d expect differences given you’re comparing 2:22 of power (or 2:55, of which 0:33 is coasting) to 3:00 of power.
Maybe contact support and ask them to help understand where the 33 seconds of coasting comes from.
Meanwhile, here’s what I did for several months:
- Record on Zwift, TR and Wahoo Bolt with Favero Assioma Duo.
- Zwift FIT file and Bolt FIT file to Golden Cheetah
- Zwift to Strava to TR
- TR to TR
Ignoring Strava, which is just a data movement hub for me, and comparing kJ, NP, Avg/Max Power, Avg/Max HR, TSS, and a host of other statistics across the whole ride and across individual intervals, allowing a small margin for sampling differences:
- All sources agree on GC
- All sources agree on TR
- GC and TR agree
Also, I don’t know about PowerAgent or any other power meter company’s analytics platform. The cycling community generally recognizes GC as a solid, reliable analytics platform, so I’m use it as a reliable reference standard. It’s also free and cross platform.