Wrong driving history, consumption, speed due to wrong timestamp, missing data

My ABRP driving history has several trips with a wrong timestamp and missing data and resulting wrong average consumption, speed and duration.

For example, my trip on 2026-03-02 14h45 (CET) has between the first and second data point a distance of 20 km and a time of 5 seconds. That’s 14000 km/h, Mach 11 😎🏎️. The visualization on the map of this trip shows a straight line between my starting position and the position 20 km further (not following any roads). The resulting summary is average speed 139 km/h (I wish my commute was that fast), while the recorded data has a maximum speed of 124 km/h.

Looking at the JSON, the first data point is where I started driving, but the timestamp is ~25 min too late. The second data point is correct in position and time. Both have tlm_type null. All next data points have tlm_type obdle. It’s possible I started ABRP when connecting the phone to the car, then switched to Google Maps, and then switched back to ABRP 25 min later. I also have Enode connected, but since that’s not the source here I doubt that’s the cause.

I’m concerned this impacts the consumption profiles ABRP builds.