Just done two hours on Zwift but somehow it’s only recorded about one hour 46/47 minutes. Did we manage to teleport through a wormhole or what? But my stats look really good having seemingly burnt those calories in less time than real time - i’ll take that! 
If you travel close to the speed of light then time slows down, so maybe that’s what happened?
2 Likes
Warp speed eh !
But it wasn’t just me, two of us experienced this because we were both on a Zoom call at the time. We started at [Uk] 07:30 we finished at 09:30 but both the main app and the Companion app showed an elapsed time of around 13 minutes less than the two hours we did.
Did you cycle near the ufo hidden under water, near volcano? 
@Paul_Churchill
Shuji at Zwift HQ here.
Were you looking at the activity in the Companion app, the web page, or are you talking about the post-ride summary in the game app?
Now that the ride’s done -would you screenshot that specific activity on zwift.com/feed and also the Companion app (if you use it)? We’d like to see what you’re seeing.
Looking at the server end - your latest session recorded as
Distance 30.6 miles
Elevation: 553.4 meters
Time: 120.0 minutes.
And this is what should be showing up on the web / ZC feeds. If there’s a discrepancy, we’d obviously like to know where it’s happening.
Shuji,
Thank you for your contact and interest.
I didn’t note the post ride summary but I can confirm that both the main Zwift app [on my iPad] and the Companion App [on my iphone] were both showing the same data. Please find attached 3 screen shots.
Best Regards
Paul
Hey there @Paul_Churchill
I asked one of my colleagues to read your game logs for clues because it didn’t make sense to me. The log file recorded 55 times during that activity that you teleported. The straight lines in your route map images you uploaded indicate where you teleported.
Pedal assist automatically applies after teleportation, and any time you spend in pedal assist does not add to your on-bike time. Some other things you should know about teleporting are on this FAQ
.
Shuji,
Thank you. So the although we knew about the distance not counting, the same applies to the time. That accounts for 9min 10 sec [55 x10] and the remaining few minutes must be coming from a) the [sometimes long] lag between pushing the teleport button and arriving next to the target rider; and b) any a use of the additional 50 sec that kicks in if you don’t start pedalling before the 10sec times out. Maybe the FAQ could be expanded to explain this?
What we were doing is a kind of HIIT climbing training where one rider goes full gas for a couple of minutes; then the second rider teleports to them and does the same whilst the first rider turns downhill and pedals gently in recovery mode before teleporting back - a bit like a Maddison team but climbing. John is stuck in the Groundhog Day syndrome that is level 100 and I’m fast approaching that glass ceiling, so we switched our efforts to climbing which is great exercise but sadly not rewarded by Zwift who reward distance but not climbing. Hence some shoot up the levels quickly by sticking to the flat routes only.
Best Regards
Paul
I had a similar experience, looking back it was on 9/21. Rode in an event, but I had to bail early. However, I purposely made sure that the elapsed time clock in the game was a decent bit past the 20 minute mark as I wanted to have a 20min power result. However the FIT file and activity in Zwift both came in at 19m48s. So seem to have lost somewhere around 45 seconds.
Does the FIT file recording of race only start after completing the lead-in?