The Vehicle Keeper Marking Register (VKM Register) provides the unique VKM and name of all keepers (EU/OTIF). It is defined in Appendix 6 part 1 of Decision 2007/756/EC.

The VKM register is updated on a monthly basis.

Since 2014, a joint OTIF/EU VKM Register is hosted by ERA and provides the VKM details in four languages (English, French, German, Russian).

The VKM register is available either in PDF or in Excel format. In case there are differences between both files, the PDF format prevails over the other format.

Any request for a new VKM, a change of the VKM and the change of the keeper´s name should be submitted to the National Safety Authority of that Member State, where the respective keeper has its place of business, using a dedicated form (Word or Excel).

What is the EVR?

The European Vehicle Register (EVR) is a web-based tool used by Keepers to submit applications for vehicle registration and by Registration Entities (REs) to manage the allocation of vehicle numbers and to record vehicle registrations and their updates.

As with the ECVVR, the EVR vehicle registration process is managed at national level.

The EVR allows:

• Vehicle Keepers and other stakeholders to request EVR accounts to Registration Entities;
• Vehicle Keepers to submit applications for vehicle registration and their updates to the RE of the relevant Member State (MS);
• REs to manage user accounts;
• Registration Entities to allocate vehicle numbers to vehicle applications submitted by Keepers;
• REs to approve or reject vehicle applications submitted by Keepers;
• Vehicle Keepers and other stakeholders to consult their vehicle data.

Please note that:

• There is no direct contact between Keepers and the Agency during the process of vehicle registration;
• Fees and charges for vehicle registration remain the competency of the relevant Member State.

Furthermore:

• Each RE should publish, at the national level, its own guidelines describing the language policy, including communication provisions; and, if any, the lists of additional fields and supporting documents;
• To explain and facilitate the use of the EVR, the Agency already published user manual for REs.

EVR state of play

A first test release of the EVR was made available to the REs in December 2020. Since then 19 Member States had interactions with the system, 8 of them have simulated data migration or tested the connection of decentralised national systems.

The EVR is live in a production environment since  the 29th November 2021 and available to the interested stakeholders at the address: https://evr.era.europa.eu.

The following Countries are now available in EVR:

• Poland
• Portugal
• Romania
• Slovakia
• Finland
• Slovenia
• Luxembourg

Users support

The Agency will support the EVR users by mean of dedicated training sessions and workshops organised as from January 2022.

The REs will receive a dedicated communication on how to proceed with the next steps, including instructions on:

• Creation of user accounts
• Support to data migration
• Connections of vehicle registers of decentralised Member States.

Business continuity of the vehicle data

In parallel, there is a need to ensure the business continuity, including the availability of the consultation of vehicle registration data.

All vehicle registrations that were available for consultation through the ECVVR will be available for consultation in the EVR once data is migrated. 

To ensure business continuity, the ECVVR will be available for regular use until the end of 2022 and beyond, as necessary.

This will allow:

• REs not yet ready to be centralised to continue registration and consultation of vehicle data via their respective national vehicle registers (NVR). 
• REs and the Agency to ensure the full testing and validation of the EVR.

The Agency will publish on its website the list of Member States whose data are available in EVR and the list of Member States whose data are still available via ECVVR. 

Access rights to ECVVR and EVR during the transition

The transition will start when the first Member State data will be available in EVR. 

During the transition process, all current stakeholders having access to vehicle data should keep their current access rights in ECVVR until the ECVVR is decommissioned. 

Independently of the status of their national data (EVR or ECVVR), each registration entity shall manage user access rights in both EVR and ECVVR (until the last MS will be using EVR and ECVVR decommissioned).

Access rights to EVR and ECVVR

Access rights to EVR are managed by each relevant Registration Entity. This is specified by Decision (EU) 2018/1614.

Therefore, we invite you to liaise directly with your relevant Registration Entity for any question regarding your user account. On the ERA Website, you may find a List of Registration Entities and their contact details.

Organisation Code

To use EVR, each Stakeholder needs to have an allocated organisation code. 

Organisation codes can be requested via the online tool available at Registers | ERA (europa.eu)

The EVR Decision 2018/1614 defines the Organisation Codes as a code consisting of four alphanumeric characters. Any Organisation accessing the EVR, or other ERA applications, where organisation code is requested, shall be assigned an organisation code.

Organisation Codes are allocated by the Agency to all interested parties, operating in the European Railway system.

The Organisation Codes are not the equivalent of RICS Company Codes issued by UIC. Each business entity operating in the Single European Railway Area and interacting with ERA hosted registers must have an allocated Organisation Code, even if it has a registered UIC RICS Code. Companies involved into TAF/TAP data exchange and companies cooperating with OSJD members, still need to obtain a 4 digit numeric code from UIC. For these companies ERA will allocate an Organisation Code with the same value as their obtained UIC RICS code.

Any request for a new alphanumeric Organisation Code or for modification of Organisation data should be submitted to the Agency online following the link: https://srm-portal.powerappsportals.com/