Skip to main content

ABRP V7.1.8 Live traffic quality is poor

iPhone 18 Pro iOS 26.6

I use ABRP Premium with Live Traffic. I have the automatic settings switched on, so real-time traffic is also switched on.

The live traffic quality of ABRP is really poor (in Germany), I mainly drive in Bavaria. Every day that I drive 83km to work, I would like to use ABRP exclusively in rush hour traffic, but since the accuracy of the traffic jam information is abysmally bad compared to Apple Maps (and Google Maps), I am forced to switch to Apple Maps every 5 to 10 minutes during the journey to find the best route with the least traffic jams and delays, and then back to ABRP.

The duration of the delay due to traffic jams and heavy traffic is sometimes estimated by ABRP to be up to 17 minutes shorter than is reality and as correctly displayed by Apple Maps or Google Maps.

For a distance of 32km, ABRP shows 33 minutes of travel time (screenshot #1), whereas Apple Map shows a realistic 50 minutes (screenshot #2), a difference of 18 minutes, and Google Maps shows also realistic 49 minutes (screenshot #3).

ABRP:

Apple Map:

Google Maps:

Unfortunately, my question about the service provider for LiveTraffic wasn't answered at the time, so I'm asking it again: Which service provider is used for the live traffic data in Germany?

Unfortunatly the quality has not been improved since nearly 2 years!

Does ABRP plan to significantly improve the quality of its live traffic data so that it is at least roughly as good as that of Apple Maps and Google Maps? @Bo (ABRP) What is the plan in this regard?

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: Awaiting Clarification12 comments

Log in to comment and vote

Comments12

  • ABRP User #2817108

    •

    Oct 7

    At this point, I’m not sure it’s necessary to keep posting links to routes for documentation purposes. I gave up on Premium with Traffic a long time ago precisely because it’s so unreliable. Besides, I constantly experience both of the issues mentioned. This looks like a general problem with your Traffic service provider.

  • ABRP User #133429

    •

    Oct 6

    I have the opposite problem when driving, yellow and red roads completely empty, and then a queue that isn’t presented on the mapping! It isn’t exactly ‘premium’

    • Linda ABRP

      Team•

      Oct 7

      Do you have a link to a plan where that happened?

  • Linda ABRP

    Team•

    Oct 7

    Can you add a link to the plan in Bavaria?

    • ABRP User #6560

      •

      Oct 7

      Since this is public, I've set the start and end points to the respective town centers.

      https://abetterrouteplanner.com/?plan_uuid=2-6ac5ec1e-6a366f741cf3f2e313526fd1

      As of 8:55 a.m., ABRP is estimating a travel time of just 53 minutes—which is far too short—whereas Google Maps is estimating a more realistic 1 hour and 5 minutes.

      ABRP:

      Google Maps:

      It’s worth noting that I drive at a constant 130 km/h on the highway (according to the speedometer) where permitted, which is about 126 km/h according to GPS. In my profile, ABRP has determined my maximum speed to be 125 km/h, which is to be expected.

      @Linda ABRP

      Do you need any further information from me for the analysis?

  • Bo (ABRP)

    Team•

    Oct 7

    Thank you for reporting this (again)! Our main traffic provider is HERE, and you can check their traffic data in the HERE Wego app (https://wego.here.com/). Checking the traffic data in your nice screenshots, qualitatively it looks reasonable, we have the same regions of slow traffic. However, our overall drive duration is way optimistic as you note - is that your main concern with the ABRP data or something else?

    • Bo (ABRP)

      Team•

      Oct 7

      And one follow-up, could you compare the drive time estimate on HERE Wego for your commute with ABRP? This is based on the same traffic data, but possibly post-processed differently.

      • ABRP User #6560

        •

        Oct 7

        I’ll post a comparison between HERE Wego and ABRP here at the next opportunity.

    • ABRP User #6560

      •

      Oct 7

      Yes, it’s the estimated travel time—which, in ABRP, is far too short when there are traffic jams or accidents compared to Google Maps and Apple Maps, which assess traffic conditions much more realistically.

      On my way to work, there are three possible routes, each with varying levels of traffic, depending on the day and time. ABRP would consistently direct me to the one route out of the three that it thinks is the shortest.

      In reality, however, the route selected by ABRP isn’t the shortest. Google Maps and Apple Maps, on the other hand, are always correct in their route selection.

      It’s a waste of time to let the app guide you along unnecessarily longer routes when there are clearly faster ones available. Google Maps and Apple Maps can guide you along the route that’s actually the fastest. ABRP can’t do that.

  • ABRP User #6560

    •

    Oct 8

    Here is the route planning with Lifetraffic, comparing the navigation systems:

    ABRP 51 min

    HERE Wego 1 hr

    Apple Maps 1 hr 1 min

    Google Maps 1 hr 1 min

    It’s clear that while ABRP takes traffic data into account by color-coding the roads (yellow, red), it does not, or at least not sufficiently, account for delays caused by traffic jams and accidents in the estimated travel time.

    I hope that with this information and evidence, ABRP is now able to identify and fix the cause of the inadequate accounting for road delays in its software, thereby raising the quality of its travel time predictions to the level of Google Maps and Apple Maps. HERE manages to do this with its own traffic data.

    @Bo (ABRP)

    What do you think?

    If you need more comparisons between HERE Wego and ABRP, let me know.

    ABRP 51 min:

    HERE Wego 1 hr:

    Apple Maps 1 hr 1 min:

    Google Maps 1 hr 1 min:

    • Bo (ABRP)

      Team•

      Oct 8

      That’s a great comparison and we are looking into what we can do to improve.

  • ABRP User #6560

    •

    Oct 14

    @Bo (ABRP)

    Do you perhaps already have some initial clues as to what the causes might be?

    The difference in travel time estimates between Here Wego and ABRP was 13 minutes today during rush hour on the rest of the route.

    Here Wego 57 minutes:

    ABRP 44 minutes: