Skip to main content

Unrealistic Travel Time Calculation (e.g., 24 km in 6 minutes)

Bug Reports

The route planning occasionally produces clearly incorrect travel time estimates. This is not an isolated incident but occurs repeatedly.

In the attached example, a route of 24 km is calculated with a travel time of only 6 minutes. This implies an average speed of approximately 240 km/h, which is not realistic under normal driving conditions.

The issue appears sporadically and is not limited to a specific route or situation, which suggests a potential problem in the time estimation logic or underlying data.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Stefan ·
2 comments

Log in to comment and vote

Comments2

  • Bo (ABRP)

    Team•

    Mar 25

    Thanks for reporting! Do you ever see this on the original plan, or only after driving for a while? Are you using waypoints or guidepoints when it happens?

    Can you give us the date for the example in the screenshot? We could try to find the exact log entry from the planner.

    • Stefan

      •

      Mar 25

      The issue occurred on March 19, 2026 at 12:11 CET. The route planning itself took place between approximately 12:00 and 12:08 CET. I cannot confirm whether the incorrect travel time was already present during the initial planning phase.

      The same problem occurred again on March 22, 2026 at 13:52 CET.

      No waypoints or guidepoints were used in either case.

      The error is visible immediately at the start of navigation. In the first example, the remaining travel time initially decreased in a plausible way down to 0 minutes. From that point onward, the app displayed 0 minutes remaining for approximately 20 km, which in reality corresponded to about 30 minutes of driving time.

      During both occurrences, I repeatedly stopped navigation, deleted the route, fully closed the app on my phone, and restarted the planning process. The result remained consistently incorrect.