EU vehicle registry fragmentation is not a technology problem. The technology to exchange structured data between government registries across borders has existed for years. Estonia built X-Road in the early 2000s, and it handles billions of inter-agency data transactions annually across multiple countries. The EU has invested in interoperability frameworks in customs, health, and tax administration. None of that infrastructure extends to vehicle registries in a meaningful way.
The fragmentation is structural. Vehicle registration is a national competence. Member states set their own data formats, update frequencies, access models, and fee structures. A directive or regulation that compelled member states to expose their vehicle registries via a common API would require political consensus that has not been achieved and shows no sign of being achieved in the near term. The European Vehicle Information System (EUCARIS) provides a legal framework for cross-border data exchange for law enforcement purposes, but its scope excludes commercial access for insurance or marketplace verification.
This piece is about what that fragmentation looks like in practice from the perspective of anyone trying to verify a cross-border vehicle history, and why the commercial solution to the problem necessarily operates at the data aggregation layer rather than waiting for a policy solution.
The Registry Landscape: What You Are Actually Dealing With
EU member states maintain national vehicle registries that differ on several dimensions that matter for commercial data access:
Data format. Some registries expose structured database records via API. Others provide data only through batch file exports. Others require web portal queries that return HTML responses. Others have no external access mechanism at all and require commercial licensing agreements with the national transport authority to receive periodic data extracts. The format variety means that any aggregation effort requires a different integration path per country.
Update frequency. The lag between a real-world event (a registration transfer, a roadworthiness inspection failure, a total loss declaration) and its appearance in the accessible registry record varies widely. Some registries update in near-real-time. Others perform batch updates overnight. Others have update cycles measured in weeks. For any signal that is time-sensitive, such as outstanding finance status or a recent registration cancellation, the update lag affects the reliability of the information returned.
Field coverage. The set of fields recorded varies by country. The standard VIN, registration number, and owner details are nearly universal. Mileage recorded at roadworthiness inspection is common in countries with mandatory periodic testing, but the inspection systems are separate from the registration registry and require separate integration. Incident and structural damage history is almost never in the registration registry; it lives in insurance claim databases that have their own access models.
Access model and fee structure. Commercial access to registry data typically requires an agreement with the national transport authority or a licensed data intermediary in each country. The terms, pricing, and permitted use cases vary significantly. Some markets have open data initiatives that allow certain registry subsets to be accessed without commercial agreements. Most do not.
The EUCARIS Exception and Its Limits
EUCARIS is frequently cited as evidence that EU cross-border vehicle data exchange is solved. It is not, and understanding why requires understanding what EUCARIS actually does.
EUCARIS (European Car and Driving Licence Information System) enables national transport authorities and law enforcement agencies to query other member states' vehicle registration and driving licence records. It is used primarily for cross-border enforcement of traffic violations and vehicle theft recovery. The queries are agency-to-agency and governed by the EUCARIS Convention and subsequent EU directives on cross-border enforcement.
Commercial entities, including insurers and marketplace operators, are not parties to EUCARIS and cannot query it. Even if they could, EUCARIS covers registration data only, not mileage history, incident records, or insurance claim data. The system that handles enforcement cooperation is categorically different from a commercial vehicle verification product.
We raise this because the existence of EUCARIS sometimes leads to the assumption that cross-border vehicle data exchange is a solved problem at the EU level. It is not. It is solved for a narrow, agency-limited, enforcement-specific use case. The commercial use case requires a different approach.
How the Aggregation Layer Works in Practice
Given the structural fragmentation, the only way to provide cross-border vehicle history verification for a commercial use case is to build and maintain separate data agreements and integration pathways for each jurisdiction you want to cover, and then aggregate and reconcile the data yourself.
This is what we do at GoodToKnow, starting with the Baltic and Nordic markets where we have the deepest coverage. The process involves:
First, establishing data licensing agreements with national transport authorities or their licensed data intermediaries. This is country-by-country commercial work, not a technical integration. The lead time and cost vary, and in some countries the agreement terms restrict the specific signals you are licensed to surface in commercial outputs.
Second, building per-country ingestion pipelines that handle the different formats, update frequencies, and data models. A field in one country's registry that is semantically equivalent to a field in another's may have different coding, different update timing, and different reliability characteristics. The reconciliation logic has to account for these differences.
Third, operating a reconciliation layer that joins records for the same vehicle across the jurisdictions you cover, resolves identifier mismatches (VIN is the primary identifier, but VIN standardization across older vehicles is imperfect), and surfaces cross-jurisdiction inconsistencies as verification signals.
This is not elegant infrastructure. It is a set of messy, country-specific integrations held together by common reconciliation logic. There is no shortcut to building it. Each new jurisdiction adds genuine integration work, not just configuration changes. We are honest about this because it explains why the product is currently stronger in some markets than others, and why extending coverage takes real time.
What Fragmentation Means for the Quality of Any Given Check
The practical consequence of registry fragmentation for a vehicle verification product is that the quality and completeness of any given check depends on the vehicle's history and the coverage of the jurisdictions it traveled through.
For a vehicle that has spent its entire life in a single country where we have deep registry integration, the check is close to comprehensive for that country's recordable events. For a vehicle that passed through three countries, two of which we have partial coverage in and one of which we have only registration data for, the check is solid for some signals and explicitly partial for others.
The responsible way to handle this is to report coverage metadata alongside signal results. A confidence score on a mileage integrity signal that reflects only domestic records should be lower than one that reflects five years of records from three jurisdictions. The caller needs to know this difference. An API that returns the same confidence score regardless of coverage depth is not telling the caller something material about the reliability of the output.
We have seen products that handle this by simply not reporting what they did not find. The vehicle history check returns a report, and the absence of cross-border history is not indicated. The caller receives an apparently complete record and does not know that two years of the vehicle's life are simply absent. This is worse than returning a partial record marked as partial, because it creates false confidence.
The Policy Horizon: Will This Change?
The honest assessment is: not soon, and not comprehensively. There is ongoing European Commission interest in broader data sharing frameworks, including vehicle data, through initiatives like the European Mobility Data Space. These are policy frameworks in development, not operational systems, and the timeline from policy framework to operational cross-border registry access for commercial use cases is measured in years.
There are also national-level initiatives in some countries to improve registry data quality and access. Estonia's e-government model, which we have written about separately, provides a data access infrastructure that makes integration more straightforward than in countries without comparable government data architecture. But Estonia is an exception, and even the Estonia model does not automatically extend cross-border queryability to other countries' registries.
The market opportunity for commercial aggregation exists precisely because the policy solution is not arriving in the relevant timeframe for insurers and marketplaces who need cross-border verification now. We are building on the assumption that registry fragmentation persists for the next several years, and that the commercial solution is the aggregation layer, not a policy fix. If the policy environment changes faster than expected, we adapt. But we are not building a product that requires policy change to work.
Why This Architecture Is Defensible as a Business
Building and maintaining country-by-country data agreements and integration pipelines is not cheap. It creates a moat that is not purely technical: it is partly regulatory (you need agreements with national authorities), partly operational (you need people who understand each jurisdiction's data model), and partly capital (the cost of integration and maintenance is real and ongoing).
The defensibility of the aggregation approach comes precisely from its difficulty. It is not the kind of problem you solve once and stop maintaining. Each country integration is an ongoing operational commitment. The quality of the reconciliation logic improves as you accumulate more vehicle trajectory data and refine the cross-jurisdiction consistency checks.
We are not arguing that this architecture is the only possible approach to cross-border vehicle data. We are arguing that it is the approach that is actually buildable today, with existing data access models and existing technology. Alternative approaches that depend on regulatory change or industry-wide data-sharing agreements may eventually produce better infrastructure. Today, the aggregation layer is what works.
