EWE Go wrong kW

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!