Which manufacturers actually deployed V2V — and what architecture each one used.
If vehicle-to-vehicle (V2V) communication means one vehicle transmitting directly to another over a local radio, with no mobile network in the path, then the list of manufacturers who have put it into series production is short — and most of the systems described as V2V in public coverage are not on it.
This audit classifies every manufacturer investigated into one of six categories, states the actual message path for each implementation, and records the negative findings alongside the positive ones. Where the public record stops, it says so rather than inferring.
Four manufacturers, three architectures, and one persistent confusion.
If “V2V” means one vehicle transmitting directly to another over a local radio link, with no mobile network in the path, then the list of manufacturers who have put it into series production is short. Volkswagen Group in Europe is the only one operating at volume. Toyota has run a smaller direct system in Japan since 2015 on a different frequency band entirely. BMW ships one in China. General Motors did it in the United States and stopped.
Everything else that gets called V2V in press coverage is one of three other things, and each is worth having — but none of them is a direct radio link between two cars:
- Cloud-mediated cooperative safety. A vehicle detects something, sends it to the manufacturer's backend over the mobile network, and the backend pushes a warning to other vehicles over their mobile connections. Mercedes-Benz Car-to-X and Volvo Connected Safety are the two production examples with the longest records.
- Infrastructure- and fleet-sourced V2X. The hazard originates from an emergency vehicle, a tow truck, a work zone or a traffic signal — not from an ordinary passenger car. Stellantis carries the largest deployment of this kind in North America; Audi has run the traffic-signal version since 2016.
- Onboard sensing. Cameras, radar and lidar detecting other vehicles. This is not V2X at any point, however sophisticated it becomes, because nothing is being communicated. It is the reason Tesla appears in this audit as a negative finding rather than as a deployment.
The distinction is not pedantry. The three architectures fail differently, scale differently, cost differently, and are regulated by different authorities. A programme that buys one expecting the properties of another has bought the wrong thing.
The four architectures, drawn.
Every implementation in this audit resolves to one of these four paths. The difference between them is the message path, not the vocabulary the manufacturer uses to describe it.
Direct cooperative V2V
Vehicle A
Detects a hard-braking event, a stationary position or its own presence, and signs a message.
Local radio
ITS-G5, DSRC, or C-V2X PC5 sidelink. Broadcast, connectionless, no operator involved.
Vehicle B
Verifies the signature against a trusted root and decides whether to warn the driver.
Latency is measured in tens of milliseconds. Coverage does not exist as a concept: either the two vehicles are within radio range or they are not. There is no subscription, no roaming, no backend, and nothing to switch off remotely. How the V2V message set works
Cloud-mediated cooperative safety
Vehicle A
Detects low friction, or the driver switches on the hazard lights.
Mobile network
The event leaves over the vehicle's cellular connection.
Manufacturer cloud
Anonymises, aggregates, geographically matches, and decides who should hear about it.
Mobile network
The warning is pushed to selected vehicles.
Vehicle B
Displays the warning. It has no idea which vehicle originated it, and does not need to.
Latency is seconds, not milliseconds, which rules out crash-imminent warnings and rules in road-condition and hazard information. It works at any range, including tens of kilometres ahead, which direct radio cannot do. It requires mobile coverage, a connected-services account, and a manufacturer willing to keep the backend running. Why the network path is a different tool
Infrastructure- and fleet-mediated V2X
Emergency vehicle, work zone or signal controller
A professionally operated asset, not a private car. It knows what it is and is trusted accordingly.
Service platform or roadside radio
Either a commercial alerting cloud, a road operator's centre, or a roadside unit broadcasting locally.
Vehicle
Receives. In the cloud variant it never transmits anything itself.
This is the architecture that actually scales first, because the value does not depend on how many other cars are equipped. One instrumented ambulance benefits every equipped vehicle it approaches. Why V2I scales linearly and V2V does not
Onboard sensing — not V2X
Camera, radar, lidar
Observes the vehicle ahead.
Onboard perception
Classifies and tracks it.
Own vehicle only
No message is sent. No other road user learns anything.
A second vehicle being detected is not a second vehicle communicating. Advanced driver assistance and automated driving belong in this row no matter how capable they are, and a fleet that learns from aggregated driving data still belongs in this row, because the learning reaches the other vehicle as a software update rather than as a message about a hazard that exists now. The strongest argument for building it this way
What was counted, what was not, and how confidence was assigned.
Manufacturers were classified into six categories. The boundary that does most of the work is between category A and category B, because those are the two that public writing most often merges.
| Category | Definition | Counted as production V2V? |
|---|---|---|
| A — Direct production V2V/V2X | Vehicles sold to customers with a direct local radio link: ITS-G5, DSRC/WAVE, C-V2X PC5 sidelink, or Japan's 760 MHz ITS band. | Yes. |
| B — Cloud-mediated cooperative safety | The vehicle originates a hazard, but the path runs over the mobile network through a manufacturer backend. | No. Real cooperative safety; different architecture. |
| C — Infrastructure or fleet V2X | The hazard originates from an emergency vehicle, work zone, road operator or signal controller rather than from a passenger car. | No. Frequently commercial and at scale, but not car-to-car. |
| D — Historical production | A genuine production system that has since been discontinued, superseded or made unavailable. | Was. The record is kept. |
| E — Pilot or announced | Field operational tests, demonstrations, fleet trials, prototype vehicles, announced future fitment. | No, in every case, however large the trial. |
| F — No verified implementation | Investigated; public evidence does not substantiate a working deployment. | No. Recorded as a negative finding. |
Four rules were applied consistently, and each of them changed at least one row:
- A radio is not a service. A vehicle containing a V2X-capable modem, or built on a platform whose supplier lists C-V2X among its capabilities, is not a vehicle running V2X. Where only the silicon could be verified, the manufacturer is not credited with a deployment.
- A supplier's design win is not an OEM deployment. Where a chipset, module or PKI vendor names a manufacturer but the manufacturer has not confirmed it, the claim is recorded with its source and marked low confidence rather than restated as fact.
- A pilot is not production, at any size. A thousand instrumented vehicles handed to fleet customers for a national trial is a large pilot, and remains a pilot.
- Where the public record stops, it stops. Chipset suppliers, certificate architectures and message profiles are stated only where a manufacturer, regulator or standards body has published them. For everything else this audit says not publicly disclosed, which is a finding in its own right.
Sources were preferred in this order: manufacturer technical documentation and press material; regulators and standards bodies; government transport agencies; consortium and public-project documentation; peer-reviewed work; reputable technical press. Every dated claim below carries its source in section 12.
Every verified implementation, side by side.
| System | Class | Path | Radio or network | From | Markets | Status |
|---|---|---|---|---|---|---|
| Volkswagen Car2X | A | Direct | 5.9 GHz, described by Volkswagen as the Wi-Fi p standard | 2019 | Europe | In production; more than two million vehicles produced |
| Toyota / Lexus ITS Connect | A | Direct | 760 MHz Japanese ITS band | 2015 | Japan only | In production, Japan-market models |
| BMW 5 Series (G60 long wheelbase) | A | Direct | C-V2X, supplier JOYNEXT | Jan 2025 | China only | In production |
| Ford China C-V2X models | A | Direct | C-V2X | c. 2021 | China only | In production in China; the 2019 United States commitment was never met |
| Cadillac CTS V2V | D | Direct | DSRC, 5.9 GHz | MY2017 | United States, Canada | Historical. Ended with the CTS after MY2019; never expanded |
| Mercedes-Benz Car-to-X | B | Cloud | Mobile network to the manufacturer backend | 2016 | Europe and other connected-services markets | In production; standard with navigation |
| Volvo Connected Safety | B | Cloud | Mobile network to the Volvo cloud | 2016 | Europe, later United States | In production on SPA and CMA platforms |
| Stellantis EVAS with HAAS Alert Safety Cloud | C | Cloud, fleet-sourced | Mobile network to the Safety Cloud platform | 2023 | United States, Canada | In production; about 1.8 million compatible vehicles activated |
| Audi Traffic Light Information | C | Cloud, infrastructure-sourced | 4G to a signal-data aggregator | 2016 | United States, later parts of Europe | In production, subscription-gated; withdrawn from one early 2017 model-year population |
| Chinese C-V2X model set | A | Direct | LTE-V2X PC5 | c. 2020 | China | In production across roughly thirty models; low fleet penetration |
Class letters refer to section 3. Deeper technical detail for each row is on its own case study rather than in additional columns, because a twenty-column table is unreadable on every device anyone actually uses.
Direct production V2V, in four places.
Volkswagen Group, Europe. The only implementation operating at a scale where the fleet-penetration problem starts to resolve itself. Volkswagen states more than two million vehicles produced with Car2X for Europe as at 27 October 2025, direct communication within a radius of up to 800 m, no mobile network needed for the exchange, notifications anonymised, and an open and standardised exchange process enabling communication across manufacturers. Fitted as an option on Golf, T-Roc, Tiguan, Tayron, Passat, ID.3, ID.4 and ID.5, and as standard on the ID.7. The Volkswagen Car2X case study
Toyota and Lexus, Japan. ITS Connect launched in 2015 on Japan's dedicated 760 MHz ITS band, with vehicle-to-vehicle and vehicle-to-infrastructure functions, initially on the Crown and Prius. Its confinement to one country is not a marketing decision: the band is a Japanese allocation, and New Zealand's transport agency has published a technical bulletin listing the affected Toyota and Lexus models precisely because operating a 760 MHz device is unlawful there. The Toyota ITS Connect case study
BMW, China. The all-new 5 Series long wheelbase, launched in China in January 2025 with V2X developed with JOYNEXT — the first BMW model with built-in V2X, and explicitly a China-market feature.
Ford, China. Factory-fitted C-V2X on China-market models including the new-generation Mondeo, EVOS, Mustang Mach-E and Edge PLUS. The same manufacturer's United States C-V2X commitment, made in January 2019 for all new US vehicles from 2022, was never delivered.
The pattern is worth stating plainly: every direct production V2V system in the world today exists inside a regulatory perimeter that made it worth doing. Europe has an allocated band, a consortium and a road-operator programme; Japan has a national ITS band and a national programme; China has spectrum, standards and pilot cities. The United States, which spent two decades on the technology, has no direct production fitment at all — only the cloud-mediated services in sections 6 and 7.
Cloud-mediated safety is real, deployed, and not the same thing.
Mercedes-Benz Car-to-X Communication. Offered since the 2016 E-Class and installed as standard in combination with navigation. When the vehicle's stability-control sensors identify low friction, that observation and its position are sent over the mobile network to the manufacturer's vehicle backend, anonymised there, and distributed to vehicles that are approaching. The customer needs a connected-services account and has to activate the service; it is included for an initial period and chargeable afterwards. Euro NCAP, assessing it, described the field generally as one where different communication strategies may be used — a mobile network, or a more direct but shorter-range radio transmission — which is exactly the boundary this audit is drawn along. The Mercedes-Benz Car-to-X case study
Volvo Connected Safety. Hazard Light Alert and Slippery Road Alert, first offered on the 90 Series in Sweden and Norway in 2016 and extended across Europe from April 2019, available on Volvo models built on the SPA and CMA platforms. When a car switches on its hazard lights the event goes to the cloud and out again to nearby connected Volvos. Volvo has been unusually explicit that the data is pooled and has invited others to join, and has shared the resulting road-condition data with municipalities and a navigation platform. The Volvo Connected Safety case study
Neither system should be dismissed. Both cover distances no radio can reach, both work on the first day a single car is equipped rather than waiting for a second one, and Volvo's slippery-road function in particular addresses a hazard that direct V2V handles badly, because friction is a property of a road segment rather than an event at a moment. What they cannot do is warn a driver about the car braking hard forty metres ahead, and no amount of backend engineering will change that.
The largest deployments are the ones where the hazard is not a car.
Stellantis and HAAS Alert. Announced on 23 May 2023: more than 1.8 million compatible Chrysler, Dodge, Ram and Jeep vehicles from the 2018 model year onward, in the United States and Canada, receiving Safety Cloud alerts through the in-vehicle Emergency Vehicle Alert System. The alerts originate from emergency vehicles, tow trucks, disabled vehicles, work zones, arrow boards and other connected roadway assets, and reach the car over its own connection through the Safety Cloud platform. The basic alert is a standard Uconnect feature with no subscription required.
This is a substantial, commercially operating V2X deployment, and it deserves the credit — it is also, unambiguously, not vehicle-to-vehicle. Nothing is broadcast by an ordinary passenger car, no passenger car transmits at all, and there is no direct radio anywhere in the path. Read as V2V it would rank as the second-largest deployment on earth. Read correctly it is the largest fleet-to-vehicle alerting deployment on earth, which is a different and more interesting claim. The Stellantis and HAAS Alert case study
Audi Traffic Light Information. Launched in the United States in 2016 with Traffic Technology Services, delivering time-to-green and, from February 2019, a green-light optimised speed advisory. Signal state comes from the traffic management systems that operate the intersections, reaches Audi's backend, and arrives in the car over its 4G connection under a connected-services subscription. Audi states the service is still offered with an Audi connect PRIME subscription in most Audi vehicles on sale today. It is the same Volkswagen Group that ships direct ITS-G5 in Europe choosing a completely different architecture for the same broad problem in a different market — and the comparison is the single most instructive thing in this audit. The Audi Traffic Light Information case study
The United States deployed it first and then dismantled the conditions for it.
General Motors equipped the Cadillac CTS with DSRC-based V2V from the 2017 model year, as standard equipment, and continued through model year 2019. In 2018 it announced plans to expand across the Cadillac fleet from 2023.
The National Transportation Safety Board's February 2024 review of the Department of Transportation's V2X deployment plan records what followed, in three sentences that between them explain the entire American position: General Motors never initiated the announced expansion; Toyota suspended its April 2018 plan to equip part of its United States fleet, citing regulatory uncertainty and the absence of deployment plans from other automakers; and Ford's 2019 plan to equip part of its fleet with C-V2X by 2022 did not occur.
Around this, the regulatory floor moved. The Federal Communications Commission reduced the transportation safety band from 75 MHz to 30 MHz, allocated the remaining 30 MHz to C-V2X alone and ordered the discontinuation of DSRC. Because the existing deployments were DSRC, infrastructure owners had to end them — and in 2021 that meant 34 states running 57 operational projects with more than 15,500 instrumented vehicles and 6,200 intersections and roadside units. In November 2023 the National Highway Traffic Safety Administration withdrew the 2017 proposal to mandate V2V in new light vehicles.
The NTSB's own assessment of what remains is blunt: the plan targets about 6 per cent of United States passenger vehicle models with 5.9 GHz capability by 2030–2034, and at the time of writing no automaker had committed to the near-term deployment the plan assumes. The Cadillac V2V case study · United States regulation in full
Large trials that are still trials.
| Programme | What it was | Why it is not production |
|---|---|---|
| Renault, SCOOP | One thousand Mégane vehicles prepared for fleet customers by December 2017, using ITS-G5 on 5.9 GHz for a French national cooperative-ITS trial. | A fleet trial with a defined scope and participant set, not a customer option on a price list. |
| Honda, Marysville and the 33 Smart Mobility Corridor | Smart Intersection using cameras above traffic signals to broadcast to connected vehicles; Safe Swarm demonstrated from 2017; a partnership with the city and the state transport department from 2016. | A test environment on public roads. No customer vehicle ships with it. |
| Tampa (THEA) connected-vehicle pilot | Toyota, Honda and Hyundai participating from 2020, with a common prototype on-board unit platform supplied by Denso. | A federally supported pilot using prototype units. |
| Jaguar Land Rover | An extended Qualcomm partnership announced in September 2023 to integrate a modem supporting low-latency V2X links, targeting vehicles from 2025. | A modem integration announcement. No shipped vehicle with an active V2X service could be verified. |
| Maruti Suzuki with IIT Hyderabad | India's first V2X research demonstration, 11 May 2022, five prototype vehicles and six use cases including a motorcycle blind-spot alert. | Explicitly a research demonstration, with the participants stating it had no connection to product planning. |
Recording these accurately matters more than it looks. Every one of them has at some point been cited as evidence that a manufacturer “has V2X”, and the aggregate effect of that citation chain is a public impression of deployment that the deployment record does not support.
Frequently assumed to have V2V, and verified not to.
Tesla. No 5.9 GHz V2X deployment, no V2X radio hardware identified in any shipping vehicle, and not a member of the industry alliance whose roster contains almost every other manufacturer named on this page. Tesla is active in the energy modes — vehicle-to-load and vehicle-to-home through Cybertruck Powershare, and vehicle-to-grid programmes with utilities in Texas and California — but those share an abbreviation with V2X rather than a technology.
The confusion is understandable and worth naming precisely, because four separate things get read as V2V and none of them is:
- Autonomy is not communication. A vehicle that drives itself extremely well is still deciding alone. Full self-driving capability makes the sensor-only row of the diagram in section 2 better; it does not move a vehicle out of that row.
- Fleet learning is not V2V. Aggregated driving data improving a model that is later shipped as an update is a development process. V2V is a message about a hazard that exists now, arriving in time to act on it.
- Robotaxi coordination is not V2V. Vehicles being dispatched and routed by a backend are clients of a central service. Two of them benefiting from data that originated in one another does not make a direct link between them, and a cooperative-safety receiver cannot use it.
- Camera-based emergency-vehicle detection is not V2X. Recognising a police car is perception. Receiving an authenticated message from one is communication.
None of this is a criticism of the architecture. There is a serious engineering argument for building a vehicle that depends on nobody else, and it is set out at length elsewhere on this site rather than caricatured. It is simply not a V2V deployment, and it should not be counted as one. Tesla and the sensor-first argument
Hyundai, Kia and Genesis. Hyundai Mobis launched production C-V2X modules in August 2023, but the customer manufacturers were not disclosed, and no Hyundai, Kia or Genesis passenger vehicle with active factory V2X could be verified. The group's public vehicle-to-everything activity is concentrated in the energy modes.
Nissan. An alliance member with trial participation in Japan. No production deployment verified in any market.
Indian manufacturers. No production V2X fitment by any Indian manufacturer could be verified. The activity is regulatory and pre-competitive: a research demonstration, an academic collaboration, and a draft standard. India's V2X framework
Truck and bus manufacturers. No series-production cooperative V2V could be verified for any major commercial-vehicle manufacturer. Platooning, the programme that would have driven it, was wound down — Daimler's truck division stopped its platooning work in 2019 after concluding the fuel case did not hold at realistic following distances. The truck-side V2X that does exist in the field is public-sector and infrastructure-flavoured: instrumented snowplough and queue-protection fleets operated by state transport departments, which belong in category C.
A negative finding is a finding. Each of these was investigated against the same sources as the positive rows, and the absence of evidence is recorded rather than filled in with inference.
Seven markets, and the reason each one looks the way it does.
| Region | Direct production V2V | What determined the outcome |
|---|---|---|
| Europe | Yes — Volkswagen Group at volume | An allocated 5.9 GHz band, a manufacturer consortium, a road-operator programme, and one high-volume manufacturer willing to fit the technology as standard on a mass model. The European Union has allocated 60 MHz for V2X, with a further 20 MHz to be shared with urban rail. |
| Japan | Yes — Toyota and Lexus | A dedicated national ITS band at 760 MHz and a national infrastructure programme, launched together. The cost is that the system is unusable outside Japan. |
| China | Yes — roughly thirty models | Spectrum allocated in 2018, a full national standards stack, twenty pilot cities and more than eleven thousand roadside units. Fitment nonetheless sat at around four per cent of vehicles in 2025, which is the clearest evidence anywhere that infrastructure alone does not create a connected fleet. |
| United States | No — none in current production | Two decades of DSRC work, one production model, a withdrawn mandate, a band cut from 75 MHz to 30 MHz and reallocated to C-V2X, and a federal plan targeting about 6 per cent of passenger vehicle models by 2030–2034. |
| South Korea | No production fitment verified | Strong supplier-side capability, including production C-V2X modules, without a verified vehicle programme behind it. |
| India | No | A regulatory framework being assembled ahead of any fitment: a draft standard, a de-licensed band, and a proposed mandate. The unusual feature is scope — it reaches two- and three-wheelers, which no other market has attempted. |
| Rest of world | No verified production | Deployments elsewhere are infrastructure projects and corridor trials rather than vehicle fitment. |
Read down the table and one variable explains most of it. Direct V2V exists where a regulator settled the radio question and left it settled long enough for a product cycle to complete. Where the radio question was reopened — as it was in the United States in 2019 — the manufacturers stopped, and they did not restart when it was closed again, because the vehicles that would have carried it had already been designed without it.
Four radios, and what each deployment actually used.
These terms are not interchangeable, and this audit does not treat them as such.
- IEEE 802.11p is the physical and link layer. DSRC is the North American system built on it with the IEEE 1609 WAVE stack and SAE J2735 messages. ITS-G5 is the European system built on the same link layer with ETSI messages and GeoNetworking. Wi-Fi p is the name Volkswagen's own customer material uses for its implementation. They share a radio; they are not one specification.
- C-V2X is the 3GPP family. PC5 is its direct device-to-device interface — the part that is comparable to ITS-G5. Uu is the ordinary path to a base station, which is what carries V2N. LTE-V2X is Release 14 onward; NR-V2X is the 5G sidelink from Release 16. A 5G modem provides Uu. It does not provide PC5 unless it was specified to.
- Japan's 760 MHz ITS band is neither of the above. It is a national allocation with its own standards, which is why an ITS Connect vehicle exported from Japan carries a radio that other countries may not permit to be operated at all.
No production deployment identified in this audit uses 5G NR-V2X sidelink. Every direct system found is either 802.11p-family or LTE-V2X PC5. The full DSRC and C-V2X comparison · Spectrum by region
What each implementation has actually published about trust.
This is the thinnest part of the public record, and the section where the temptation to infer is strongest. A direct V2V system operating in Europe is required by the applicable specifications to sign every message and to rotate pseudonymous certificates; that is a property of the standards, not an observation about any particular manufacturer's implementation. The two claims must not be merged.
| System | Publicly stated | Implied by the architecture but not confirmed by the manufacturer |
|---|---|---|
| Volkswagen Car2X | Notifications are anonymised; the exchange process is open and standardised, enabling communication across manufacturers. | Message signing, certificate enrolment and pseudonym rotation to the European C-ITS security specifications. A PKI supplier publishes a customer claim naming Volkswagen; Volkswagen has not corroborated it, and it is recorded as a supplier statement. |
| Toyota ITS Connect | Not publicly disclosed in the material reviewed. | Whatever the Japanese ITS profile requires. No manufacturer statement of the credential architecture was found. |
| Cadillac V2V | Not publicly disclosed at the level of certificate architecture. | The IEEE 1609.2 security services that the WAVE stack defines. |
| Mercedes-Benz Car-to-X | Data is anonymised in the backend; the service requires an authenticated connected-services account which the customer must activate. | Ordinary transport security between vehicle and backend. There are no over-the-air message certificates to manage, because there are no over-the-air messages between vehicles. |
| Volvo Connected Safety | Road-surface information is collected anonymously; shared data is anonymised before it reaches third parties. | As above. |
| Stellantis with HAAS Alert | Not publicly disclosed at protocol level. | Platform-authenticated senders. Trust is established commercially, by admitting professional fleets to a platform, rather than cryptographically at the receiver. |
That last row contains the structural point. The two families place trust in different places. A direct V2V receiver must be able to decide, offline and in milliseconds, whether an anonymous message from an unknown vehicle is worth acting on — which is why the entire public-key apparatus exists. A cloud-mediated system moves that decision into a backend that already knows who every participant is, and pays for it with latency, coverage dependence and the requirement that somebody keep operating the backend. Why V2X identity is harder than web identity · The two trust models compared
Six things the deployment record teaches that the standards do not.
- A cloud-mediated feature has a backend compatibility lifetime. Audi's own technical service bulletin, filed in May 2023, records that traffic-light information stopped working on 2017 model-year A4 and Q7 cars built before a specific production week, because those vehicles carry software no longer compatible with the backend that provides the data, and that there is no software or hardware update that resolves it. The service itself continues; it was that population that lost it. A direct-radio system has no equivalent failure mode; its exposure is certificate expiry, which is a solved problem with a known remedy.
- Spectrum policy is product policy. Toyota's system cannot leave Japan, and the United States industry stopped when its band was reopened. Nothing in either case was an engineering failure.
- Infrastructure does not create a fleet. China allocated spectrum in 2018, built more than eleven thousand roadside units and ran twenty pilot cities, and vehicle penetration was still around four per cent in 2025. Roadside deployment and vehicle fitment are separate problems and need separate instruments.
- The first deployable value is not car-to-car. Every large operating deployment in this audit that is not Volkswagen's derives its value from an asset that is not an ordinary passenger car — an ambulance, a work zone, a signal controller, a road-condition aggregate. That is what linear returns look like next to quadratic ones.
- An option box is a fitment strategy. Volkswagen reached two million vehicles by making the function standard on one mass model and a cheap option across the rest of the range. The manufacturers who offered it only on a flagship never reached a density at which anything happened.
- Cross-manufacturer interoperability is the whole point and is almost never tested in public. Volkswagen states its exchange process is open and standardised across manufacturers. In Europe that claim can in principle be exercised. In the cloud-mediated systems it cannot: a Volvo warns Volvos, a Mercedes warns Mercedes, and the pooling that Volvo has publicly invited has no equivalent in the direct world because the direct world got interoperability for free from the standard.
What a market with no fitment should take from a record like this.
India is in an unusual position: it is assembling a regulatory framework before there is anything to regulate. There is no production V2X fitment by any Indian manufacturer, effectively no roadside estate, and no domestic on-board or roadside unit manufacturer. That is a disadvantage in every respect except one — nothing has been built yet that a later decision would strand.
Five observations from the global record apply directly:
- The mandate route is the only one that has ever solved the penetration problem from a standing start. Every market that got direct V2V got it either through regulation or through a single manufacturer with enough volume to move the number alone. India has no manufacturer in the second category, which leaves the first.
- Fleet-wide fitment inverts the economics that stopped everyone else. The reason early adopters failed is that they paid full cost for near-zero benefit while penetration was low. A simultaneous mandate is the only instrument that skips that phase, and it is the strongest argument for the approach.
- Settle the radio and leave it settled. The American record is a demonstration of what reopening the question costs: the deployments stopped, and they did not restart.
- Direct V2V delivers a real subset of value without any roadside estate. Emergency brake alert, forward collision warning and wrong-way driving alert need no infrastructure at all. That matters in a market where the roadside estate does not yet exist.
- The trust architecture is on the critical path, not after it. Every direct system in this audit needs a receiver able to decide offline whether an anonymous message is trustworthy. A market fitting the whole fleet at once needs that apparatus working from the first vehicle, not retrofitted once a problem appears.
The Indian framework is a set of proposals at varying stages, not an enacted mandate, and this site tracks its actual status rather than its headline. India's V2X regulation in detail
Where each claim comes from.
- Volkswagen Group — A milestone for greater road safety: more than two million vehicles produced with Car2X, 27 October 2025. Vehicle count, Wi-Fi p, 800 m, no mobile network, anonymisation, user activation, cross-manufacturer exchange, model list.
- Toyota Motor Corporation — Toyota Bringing Advanced ITS Technology to Mass-market Models, 2015. ITS Connect launch, 760 MHz, V2V and V2I functions, initial models.
- Waka Kotahi NZ Transport Agency — Vehicles fitted with ITS Connect. Regulator confirmation of the 760 MHz band, the affected Toyota and Lexus models from 2015 onward, and the New Zealand licensing position.
- National Transportation Safety Board — Response to the USDOT V2X Deployment Plan, 2 February 2024. Cadillac CTS model years, the unexecuted GM expansion, Toyota's suspension, Ford's unmet commitment, the FCC band reduction, the 2021 infrastructure figures, the NHTSA withdrawal, and the 6 per cent target.
- Audi of America — Technical Service Bulletin 91 23 91, 2070216/1, 5 May 2023, filed with the National Highway Traffic Safety Administration. Withdrawal of Traffic Light Information Online from early 2017 model-year A4 and Q7 vehicles for backend incompatibility.
- Euro NCAP — Advanced Reward assessment of Mercedes-Benz Car-to-X Communication. Independent assessment of the system and of the distinction between network-mediated and direct short-range strategies.
- Volvo Cars — Volvo models across Europe to warn each other of slippery roads and hazards, April 2019. Europe-wide launch, cloud architecture, SPA and CMA platform coverage, 2016 origin.
- HAAS Alert — Industry-leading V2X activation equips 1.8 million Stellantis vehicles with Emergency Vehicle Alert System, 23 May 2023. Vehicle count, brands, model years, markets, alert originators and the platform path.
- BMW and JOYNEXT — BMW launches the all-new 5 Series with V2X technology in China, April 2025. First BMW model with built-in V2X, China market, supplier.
- Renault Group — “Renault works with SCOOP to prepare infrastructure for tomorrow’s autonomous, connected cars”. The thousand-vehicle ITS-G5 fleet trial.
External links are provided so that every figure can be checked at its origin. They do not imply any relationship with, or endorsement by, the organisations named, and the trademarks referenced belong to their respective owners.
This is a dated record, not a permanent one.
Every row above is a statement about what could be verified on the review date printed at the foot of this page, and several of them are actively moving. Model availability changes with the model year. Systems are withdrawn quietly and rarely announced. Chinese fitment is rising from a low base. A regulator can turn a category F into a category A in a single notification.
If a claim on this page is wrong, or if a manufacturer has published something that would change a classification, the correction address at the foot of the page reaches the person who maintains it. Corrections are made in the source and the review date moved with them.
Developing a V2X on-board unit, roadside unit or vehicle integration programme? Ambimat's V2X work is hardware, device-side security and integration engineering. V2X engineering capabilities
The individual studies.
Volkswagen Car2X
Direct 5.9 GHz communication at two million vehicles, and how the fitment strategy got it there.
Toyota ITS Connect
A national ITS band, a decade of production, and a system that cannot leave the country.
Cadillac V2V
The only DSRC vehicle America ever sold, and the regulatory sequence that ended it.
Mercedes-Benz Car-to-X
Cooperative safety over the mobile network, and why that is a different product.
Volvo Connected Safety
Hazard lights and road friction, pooled in a cloud, and an open invitation nobody took up.
Stellantis and HAAS Alert
1.8 million vehicles receiving alerts from emergency fleets. Not one of them transmits.
Audi Traffic Light Information
Signal data over 4G since 2016, still offered today — and a service bulletin showing what a backend outliving a car looks like.
The V2X market
The commercial picture behind the deployment record: who supplies it, and who walked away.
V2V
The message set, the applications, and the quadratic penetration problem underneath all of it.
Questions this page answers.
Which cars have V2V communication?
In Europe, Volkswagen Group models with Car2X: Golf, T-Roc, Tiguan, Tayron, Passat, ID.3, ID.4 and ID.5 as an option and ID.7 as standard, representing more than two million vehicles produced. In Japan, Toyota and Lexus models with ITS Connect on the 760 MHz band. In China, the BMW 5 Series long wheelbase, several Ford models and roughly thirty models in total across manufacturers. In the United States, no direct V2V is currently in production — the cloud-mediated services that do ship there are a different architecture.
Does Tesla have V2V or V2X communication?
No production vehicle-to-vehicle system could be verified. There is no 5.9 GHz V2X deployment, no V2X radio hardware identified in any shipping vehicle, and Tesla is not a member of the main industry alliance. Autonomous driving, fleet learning, robotaxi coordination and camera-based emergency-vehicle detection are each frequently mistaken for V2V, and none of them involves a vehicle transmitting a cooperative safety message. Tesla is active in the energy modes, which share the abbreviation but not the technology.
Is Mercedes-Benz Car-to-X the same thing as Volkswagen Car2X?
No, and the similarity of the names is the most common source of confusion in this subject. Volkswagen Car2X is a direct 5.9 GHz radio link between vehicles, which Volkswagen states does not use the mobile network. Mercedes-Benz Car-to-X sends the observation over the mobile network to the manufacturer's vehicle backend, which distributes warnings to other vehicles over their own connections. Both are production cooperative safety systems; only the first is direct vehicle-to-vehicle.
Why did General Motors stop building V2V cars?
The Cadillac CTS carried DSRC as standard equipment from model year 2017 through model year 2019, in anticipation of a United States mandate that was never issued. The National Transportation Safety Board records that the announced Cadillac fleet expansion was never initiated, that Toyota suspended its own United States plan citing regulatory uncertainty, and that Ford's 2022 commitment did not occur. The Federal Communications Commission then cut the safety band from 75 MHz to 30 MHz, allocated the remainder to C-V2X alone and ordered DSRC discontinued.
Is a 5G-connected car a C-V2X car?
No. C-V2X has two distinct interfaces. Uu is the ordinary path to a mobile base station, which any connected car has and which carries vehicle-to-network services. PC5 is the direct device-to-device sidelink, and it is the part comparable with ITS-G5 or DSRC. A vehicle with a 5G modem has Uu. It does not have PC5 unless the modem was specified for it and the vehicle runs V2X applications over it.
How many vehicles have V2X worldwide?
No reliable global total exists, and none is stated here. The largest verified single figure is Volkswagen's: more than two million vehicles produced with Car2X for Europe, stated in October 2025. The largest verified receive-only activation is about 1.8 million compatible Stellantis vehicles in North America receiving emergency-fleet alerts through a commercial platform, which is not vehicle-to-vehicle. Chinese fitment was reported at around four per cent of vehicles in 2025.
Last updated 2026-09-08 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: neel.shah@ambimat.com