Skip to main content

Issues with Destination Search Accuracy and Travel Time Estimates in ABRP.

Questions

  1. The first issue I’m facing is that when I try to search for a destination in ABRP, the information returned is often inaccurate, or it simply can’t find the location I’m looking for.


    However, if I do the same search in Google Maps or Waze, they find the information right away, even for well-established locations in my area. I’d like to know how ABRP conducts its searches, what data sources it uses, and if there’s a way to connect it to Google Maps or Waze to improve the accuracy of the search results.

  2. The second issue I’m having is that even when I do find my destination, for instance a place I regularly travel to and have saved in ABRP, the estimated travel time is way off. For example, a trip that actually takes about 30 minutes is estimated by ABRP to take an hour and a half.


    There are no stops, it’s a direct route, and I don’t even need to charge along the way. Other OBD2 data, like battery percentage, speed, and other values, seem to be accurate, though.

Posted by Benoit Martin ·
1 comment

Log in to comment and vote

Comments1

  • Thomas

    •

    Jun 30, 2025

    Hi @Benoit Martin ,

    I will investigate it. Can you provide me with an address/destination not found when searching, and/or returns inaccurate information? We will correct it if we find the source.

    And please send me the plan in your point 2 (“estimated by ABRP to take an hour and a half”)