Shell is making a concept EV that will charge in under 10 minutes


Shell may be synonymous with oil and gas, but it’s still hoping to lead the way with electric cars. The company has previewed a Triple 10 Challenge Concept Car that it hopes will set new standards for EV charging, efficiency, and climate-friendliness.

The compact SUV is intended to meet the three goals of its namesake Triple 10 Challenge. It should charge from 10% to 80% in under 10 minutes, achieve efficiency of 10km (6.2 miles) per kilowatt-hour, and offer a lifetime CO2 impact of 10 metric tons (about 9.8 imperial tons).

The fast charging will come by immersing the battery cells in non-conductive cooling fluid that’s better at distributing heat, improving both sustained charging speeds and overall efficiency. That, in turn, lets Shell use a lower-capacity battery to save weight without compromising on range.

Mobility VP Cara Tredget tells Auto Express that the company is aiming for a weight under 1,000 kg (about 2,204 lbs.), making it far lighter than the 3,500 lbs. to 5,000 lbs. you typically see for smaller EVs.

Will Shell sell its EV concept?

Don’t expect a production model

Shell Triple 10 Challenge Concept Car EV sketch
Shell Triple 10 Challenge Concept Car EV sketch.
Credit: Shell

Shell will fully reveal the Triple 10 Challenge Concept Car in June, and has already shared a sketch (shown here). This will be a fully drivable EV. It won’t be a clay model or a demo-only design.

However, Shell has already noted that it won’t make a production version. As Tredget explains, the concept exists to show what can be done with technologies that are “available and scalable now,” rather than relying on exotic or unrealized breakthroughs.

Companies like Tesla and Mercedes are already using immersion cooling in vehicles like the Semi truck and AMG GT 63 S E-Performance hybrid. Chinese manufacturers like BYD have already designed batteries that can charge in as little as five minutes, and solid-state batteries also promise to cut charging times even as they reduce weight. However, those technologies are either in limited use or are still on the horizon.

The Shell concept car theoretically encourages automakers to think differently, lowering EV costs and spurring adoption.

Shot of the engine under the hood of a 2026 Hyundai Tucson Hybrid.


Your driving habits determine if a hybrid is worth the premium—here’s how to know

Do you really benefit from the tech you are shelling out more to have?

Why does Shell care about EVs?

It’s good for business in the long run

A Kia Niro EV charging at a Tesla Supercharger stall. Credit: Bertel King / How-To Geek 

It may seem odd for Shell to devote attention to EVs. Its revenues are still heavily dependent on oil. $31.6 billion of its $56.1 billion in 2025 adjusted EBITDA (earnings before interest, taxes, depreciation, and amortization) came from the combination of oil extraction and chemical production.

However, Shell also has growing businesses in charging, EV lubricants, and renewable electricity. The energy giant knows that electric cars and zero-emissions power are gathering momentum despite some rough markets, with certain countries and regions expecting to phase out combustion engine car sales as soon as 2035. The Triple 10 Challenge Concept Car could help boost sales across these categories and ensure that Shell is ready when oil is less vital.


The right concept at the right time

Shell also has incentives to promote EVs even if its oil business fares well. Its revenues have been highly volatile as the COVID-19 pandemic, the conflict in Iran, and other issues have led to large oil price changes. Electric cars and their infrastructure could provide a relatively stable income source.

Source: Auto Express.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link