EVwire Brief: Stellantis has announced that it is adopting the North American Charging Standard (SAE J3400) for select Stellantis EVs in North America, Japan, and South Korea, giving future access to more than 28,000 Tesla Superchargers across all five countries.
Tesla Supercharger network availability will start in 2026 with existing North American BEVs, such as Jeep Wagoneer S and Dodge Charger Daytona, followed by the 2026 Jeep Recon and other future products.
Context:
Tesla writes: “Car manufacturers are transitioning to NACS in Japan and South Korea, improving ease of use and reliability by eliminating connector-side locking found in CHAdeMO and CCS1”
Max de Zegher, one of the leaders of the Tesla Supercharging team, gives us more context on why exactly the other markets are now involved:
“Car manufacturers and consumers want clarity on a standard for Japan (NACS & CHAdeMO market) and South Korea (NACS & CCS1 market). Building CHAdeMO vehicles just for Japan, or CCS1 vehicles just for South Korea, no longer makes sense.
With such a strong NACS presence already (in Japan nearly all 150 kW+ stations are NACS Tesla Superchargers), and a better customer experience, it makes sense to converge to NACS asap.
We hope to accelerate this clarity, through large car manufacturers like Stellantis now adopting NACS, for both Japan and South Korea.”
By the way, Stellantis is not the first one to announce the NACS adoption for its electric vehicles in Japan. Sony Honda Mobility and then Mazda have also announced this earlier this year.
As for the US, the Tesla NACS website now shows that “Supported” carmakers for the network are: Ford, Rivian, General Motors (GM), Volvo, Polestar, Nissan, Lucid, Mercedes-Benz, Hyundai, Genesis, Kia, Honda, Acura, JLR, Audi, Porsche, Toyota, Volkswagen (VW).
And under the “Coming Soon” are BMW & Subaru.
I guess Tesla needs a new section for the rest of the world adoption soon…
Source: Stellantis, Max de Zegher, EVwire, Tesla
DIG DEEPER into the charging industry news with our dedicated ⚡ CHARGINGWIRE page.
