ABRP incorrectly displays estimated times when clicking on a segment of a trip.

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/abrp-incorrectly-displays-estimated-times-when-clicking-on-a-segment-of-a-trip/
———————————————————————————
ABRP incorrectly displays estimated times when clicking on a segment of a trip. See the following route as an example:

https://abetterrouteplanner.com/?plan_uuid=f32832d3-719d-415a-94e9-64713d2ac226

Trip calls for a drive from Moncton, NB Canada, ending just before the United States Border. This trip would require one supercharger stop in Quispamsis, NB Canada.

The actual times listed for the waypoints on the lefthand side of the website / iOS app appear to correctly reflect expected timeframes, I.E:

• Leaving Moncton @ 12PM.
• Arriving at the Quispamsis Supercharger @ 1:18PM.
• Leaving the Quispamsis Supercharger @ 1:52PM.
• Arriving at destination (just before Canada/US (Maine) border @ 3:09PM.

However, there seems to be an issue with time calculations if one clicks into a particular segment of a route displayed on the map.

For example, if I click on the route segment between Moncton and Quispamsis (but just before arriving at the Quispamsis supercharger, see the yellow circle in the first screenshot) it accurately reflects the time at that point in the route would be approx. 1:17PM time as one would expect. This is in line with the estimated arrival time displayed in the waypoints for the Quispamsis supercharger (circled in green in the first attached screenshot).

The thing is, after having stopped at the supercharger for ~29 minutes, you'd be hitting the road again at around 1:52PM. The weird thing is my second screenshot shows the second leg of the trip onwards (I.E. IMMEDIATELY after hitting the road from the Quispamsis supercharger mentioned above), it estimates that the time at that position along the route would be 4:25PM (circled in red, again in the second attached screenshot).

This makes no sense - telling me at that section of the route it would be 4:25PM, even though the final destination of the trip was (correctly) predicting for us to arrive at 3:09PM according to the final waypoint.

Any thoughts on this? It makes it difficult (other than using the time estimations displayed in waypoint overview) to precisely determine what the time would be at a particular point along a route.