Reported September 24, 2026.
Geely says its next-generation charging system can take an EV battery from 10 percent to 70 percent in four minutes and 30 seconds.
BYD previously announced a system capable of charging from 10 to 70 percent in five minutes, putting the two companies close together on the headline charging metric.
The company says the test vehicles reached 97 percent charge in less than nine minutes.
The announcement comes as Chinese automakers compete on charging speed as well as vehicle range and price.
Geely says its software predicts battery temperature and adjusts power delivery during charging. The objective is to push power high without creating excessive heat or accelerating battery degradation.
The system can deliver up to 2,250 kilowatts of peak charging power. Geely tested the technology on a Zeekr 001 sedan and a Lynk & Co 10 hybrid.
Why the change matters
Geely’s result is a laboratory and product-development claim, not a promise that every charging session will take four minutes and thirty seconds. Real-world performance will depend on battery temperature, station availability, grid conditions and the vehicle.
Charging speed is becoming a hardware-and-software problem. Delivering more electricity is easy to describe, but batteries cannot accept unlimited power at every temperature and state of charge.
The engineering problem
Drivers care about the time spent at the charger, but networks also need to consider how many vehicles can charge simultaneously. A very fast charger is only useful if enough high-power stations exist.
That is why thermal prediction matters. The charging system has to decide how much power the battery can safely accept at each moment.
Automakers are therefore turning charging into part of the product identity. The car, battery management software and charging network increasingly form one experience.
Ultra-fast charging also shifts pressure onto the charging station. A 2,250-kilowatt system requires substantial electrical infrastructure, cooling and grid capacity.
Ultra-fast charging changes the role of the battery-management system. The software has to decide how much power the cells can accept while keeping temperature and degradation within acceptable limits.
The charging station also becomes a major piece of infrastructure. A multi-megawatt charger needs grid capacity, power electronics and thermal management.
Drivers will experience the benefit only if high-power stations are widely available. A spectacular laboratory charging time has limited value when the nearest compatible station is hundreds of kilometers away.
Competition between automakers is pushing charging technology forward, but the real test will be consistent performance across different climates, battery states and vehicle models.
The practical takeaway
The announcement is important because it changes a real part of the technology stack rather than simply adding another specification. The next few months will show how the technology performs outside controlled demonstrations and how quickly the surrounding ecosystem adapts.
Battery chemistry will ultimately limit how far charging speeds can go. Power electronics and software can optimize the process, but the cells still have physical constraints. Future progress will therefore depend on chemistry, thermal design and charging infrastructure as much as on software.
The numbers behind the announcement
The headline number is useful, but it needs context. Product specifications and incident counts describe a specific test, deployment or reported event. They should not automatically be treated as universal performance figures. Conditions, availability and implementation details can materially change the result.
For readers following the technology closely, the useful signal is what changes after the announcement. New software will be tested by users, hardware will face real workloads, and security claims will be challenged by real deployments. That follow-through will determine whether today’s announcement becomes a durable technology shift or simply another short-lived product cycle.
The headline feature is only one part of the story. The surrounding infrastructure often determines whether a technology is useful in practice. That includes the software layer, the hardware it runs on, the permissions around it and the systems it has to communicate with. A product can look impressive in a controlled demonstration and still behave very differently once it is exposed to real users and unpredictable inputs.
Another detail worth watching is the gap between availability and capability. Companies frequently announce a feature before every user can access it, and early versions may be limited by geography, hardware, account type or preview status. That distinction matters because a capability shown in a demonstration is not necessarily a capability that an ordinary customer can use today.
The competitive effect is broader than the company making the announcement. Rivals now have a reference point, suppliers have a new target and customers have another option to compare. That can accelerate development across the category, but it can also create pressure to ship features before the surrounding infrastructure is mature.
For developers, the announcement creates a more practical question than whether the technology is impressive: where does it fit? The strongest products usually remove an existing bottleneck rather than adding another dashboard. If a feature reduces a repeated task, improves a slow stage in a workflow or makes an expensive resource more efficient, adoption has a clear reason to follow.
There is also a maintenance cost behind the announcement. Software needs updates, hardware needs replacement and cloud services need monitoring. For enterprise deployments, those costs include security reviews and access management. For consumers, they include battery life, subscriptions and the reliability of updates. The long-term experience is shaped by these ordinary details more than by the launch presentation.
The technology is also arriving at a moment when users are becoming more selective about automation. People want systems that save time, but they do not want to lose control of important decisions or data. That makes transparency, confirmation and recovery increasingly important product features rather than secondary settings buried in an advanced menu.
One practical consideration is verification. Early reports often combine company statements, tests, customer observations and independent analysis. Those pieces answer different questions. A company can establish what it built, while independent users reveal how it behaves under normal conditions. Keeping those distinctions clear makes a technology story more useful than simply repeating the launch claim.
The same distinction applies to numbers. A capacity figure, charging time, funding amount or incident count can be accurate while still being easy to misunderstand without context. Test conditions, timing and definitions matter. Readers should be able to tell whether a number describes a controlled demonstration, a planned capability or an observed production event.
The next few weeks should provide better evidence than the announcement itself. Products will move from preview to broader availability, security teams will publish more technical details, and customers will discover edge cases. Those follow-up signals are often where the real story becomes clear because they show whether the underlying technology survives contact with everyday use.
That makes this development worth watching without treating the launch as the final word. Technology markets move quickly, but the infrastructure around a new product moves more slowly. Adoption, interoperability, reliability and operational cost will decide how much of the announced capability becomes part of normal computing rather than remaining a demonstration.
For teams deciding how much attention to give the development, the useful approach is to separate the immediate event from the broader trend. The event may be a product launch, a research result, a security incident or a financing announcement. The trend is the underlying change in technology, infrastructure or user behavior that made the event possible. Both matter, but they answer different questions.
What to watch
- Broader availability and real-world deployments
- Independent testing and operational results
- Changes to the surrounding software and hardware ecosystem