Join our newly restarted iOS Beta and try out new features sooner: https://testflight.apple.com/join/PDzBYbJw
Read more about ABRP beta at Installing the ABRP Beta version
Fully electric pick up truck. Commonly used in south and Central America. Type 2 connector with 332 kms of range in NEDC cycle.
after planning a trip it would be helpful to schedule it - say tomorrow at 10am - when it gets pushed to the vehicle. likewise it would be good to save a route so it can be recalculated and sent to the car
The timeliness of traffic disruption updates needs significant improvement. There has been a full road closure in our city for the past 6 months: the aprp navigation app keeps directing you there, and if you’re not familiar with the area, you end up right in front of the closure. What a shame! On the positive side: the improved OBD connection significantly enhances the live driving data!
Funny that ABRP is owned by Rivian, but Rivian is missing from charge cards for those of us who don’t own a Rivian for non “Rivian only” sites. Please add. Thanks
My Skoda Enyaq Coupe RS 2024+ Crystal face suddenly shows the picture of regular Enyaq and with non-crystal face after some ABRP-update.
subscription to premium stopped while these settings were on and they remained on If I want to disable it says I need premium. I would expect this settings to return to the default false when premium ended.
CRITICAL DATA ISSUE: Multiple Hyperchargers incorrectly listed as 20 kW in Germany Hi ABRP Team, I am reporting a serious, systematic data mapping issue regarding the EWE Go charging network in Germany. Multiple high-power charging locations (Hyperchargers, which actually provide 150 kW, 300 kW, or even up to 400 kW DC) are incorrectly listed in the ABRP database with a maximum charging power of only 20 kW. Because of this incorrect data, the ABRP routing algorithm automatically filters these stations out during long-distance route planning. This is not an isolated incident, as I have verified this behavior across at least 4 different EWE Go stations already, including their ultra-fast charging sites. Why this is a high-priority issue (Network Importance): EWE Go is one of the top 5 largest public charging infrastructure operators in Germany, running over 3,000 active charging points nationwide. They are the absolute market leader in north-west Germany and maintain a massive fast-charging partnership covering around 700 McDonald's (McDrive) locations with high-power chargers up to 400 kW, alongside a major expansion partnership with Lidl stores. Having one of Germany's core highway and everyday fast-charging networks completely broken/filtered out in ABRP severely impacts the routing quality for thousands of German EV drivers. Specific example sites for your reference: Site 1: Berkaer Straße 73, 99425 Weimar, Germany Site 2: Heinrich-Hertz-Straße 2, 06667 Weißenfels, Germany Site 3: Sollnitzer Allee 1, 06846 Dessau-Roßlau, Germany Site 4: Felix-Wankel-Straße 38, 70794 Filderstadt, Germany Problem in ABRP: All these sites are listed as 20 kW, but they are actually High-Power Charger (HPC) network sites. Could you please check the backend data feed / roaming interface (e.g., Hubject) for the EWE Go network in Germany and update the maximum charging power capabilities globally? Thank you for your help and for keeping the database accurate!