Skip to main content

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

Bug Reports

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.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Tomas ·
Status: Awaiting Clarification5 comments

Log in to comment and vote

Comments5

  • Tomas

    •

    Apr 30

    I can still reproduce this on 7.0.5 (5819). (That’s the same version number as my earlier comment, but a higher build number.)

    For one drive, it shows consumption of 518 Wh/km where in fact I used around 190 Wh/km. On another drive it shows 55 km trip distance where it was 80 km, while the trip duration is correct. This makes the drive history useless for both distance and consumption. I also wonder how accurate it can plan trips if it has these wild ideas about my consumption and speed.

  • Linda ABRP

    Team•

    Mar 24

    Hi

    When you have missing data that’s because we don’t get enough data. That’s also why you have straight lines on the map. You write that you are using Enode and

    unfortunately Enode and Kia cars are not always working very good.

    • Tomas

      •

      Apr 7

      Hi

      I have disabled the Enode integration a bit more than a week ago, now working with OBDII only, and still have this issue.

      I'd understand if the drive history was simply incomplete.

      However the app shows not only incomplete, but very wrong data.

      My 6:02 PM trip today was 14 kWh/100km according to the car dashboard, and 7 kWh/100km according to ABRP!

      The app must be fixed to log correct timestamps for the locations, and it must be fixed to ignore periods without data when calculating averages.

      Kind regards,

      Tomas

  • Tomas

    •

    Mar 18

    I can still reproduce this on 7.0.5 (5793).

    Is there a reason this is still “Pending"?

  • Tomas

    •

    Mar 12

    I can still reproduce this today with version 7.0.4 (5790).

    Is there a reason this is still “pending”?