My bookmarksSign up free

Commission Implementing Regulation (EU) 2026/253 CHAPTER 2 — GENERAL RULES AND PRINCIPLES

Article 4–Article 15 · 12 articles

Compiled from an official source version. Later amendments or repeals may not be reflected; the official text prevails. · Read the official text ↗

Data sharing between telematics stakeholders and rights to access data

Article 4

1.   Where telematics stakeholders involved in the same rail transport services and related processes referred to in Article 2(1) have rights or obligations deriving from legal or contractual provisions for those processes, they shall grant each other access for use or share the data specified in the Annex that are necessary to carry out those processes. Except for the processes referred to in Article 2(1), point (c)(i), the rights and obligations referred to in the first subparagraph may also result from the operational responsibility in those processes, of any entity involved. 2.   Upon reasoned request of the Commission, a Union body or a public sector body, telematics stakeholders that hold data specified in the Annex shall grant free of charge direct access to specific raw data for one of the following purposes: (a) the monitoring of the establishment of the single European rail area or the trans-European transport network; (b) the development of rail interoperability and safety in the Union; (c) the monitoring or auditing of the flow of passengers or freight in the Union.

Access to train traffic data and train composition data

Article 5

1.   In addition to the obligations set out in Article 4 of this Regulation, each infrastructure manager or, where relevant, an operator of rail freight service facilities shall grant telematics stakeholders pursuant to Article 4(1) access via a common Union web user interface (‘web UI’) in the area of traffic management referred to in Article 14(5) of this Regulation, and as part of the minimum access package laid down in point 1 of Annex II to Directive 2012/34/EU, to the following raw data in accordance with the specifications and access conditions set out in Annex: (a) working timetable data, referred to in point 2.3.10 of the Annex to this Regulation, generated by the infrastructure managers or, where relevant, the data holder; (b) train traffic data, referred to in point 2.6 of the Annex to this Regulation, generated by the infrastructure managers as holders of that data; (c) train composition data, referred to in point 2.5.1 of the Annex to this Regulation, received from railway undertakings as holders of that data; (d) historic record of train data, referred to in point 2.7 of the Annex to this Regulation. 2.   Access to the data referred to in paragraph 1 shall be public and free of charge via a publicly accessible common Union web UI. 3.   Paragraph 2 shall not apply to transport of dangerous goods subject to the provisions of Directive 2008/68/EC of the European Parliament and of the Council  ( 35 ) . 4.   In the case of freight rail transport services, paragraph 2 shall only apply where a freight railway undertaking chooses to disclose the data referred to in paragraph 1 in respect of some or all of its transport services on a voluntary basis. 5.   The common Union web UI referred to in paragraph 1 shall ensure an automated implementation of the access restrictions and limitations referred to in this Article as specified by the data holder. 6.   The provisions of this Article shall neither apply to rail transport services for the armed forces nor to other rail transport services subject to security measures adopted by a Member State where such services are operated.

Access to data for journey planning of passenger rail transport services and to tariff data

Article 6

1.   Each passenger railway undertaking, or, where relevant, the competent authority as defined in Article 2, point (b), of Regulation (EC) No 1370/2007 of the European Parliament and of the Council  ( 36 ) , or the data holder, shall grant public and free of charge access to data specified in points 4.2.1 and 4.4 of the Annex regarding the passenger timetable of the rail transport service that it operates and for corresponding conditions of carriage, respectively. Access shall be granted at least via the national access points in accordance with the specifications and access conditions set out in the Annex. 2.   Each station manager, or, where relevant, the infrastructure manager or another entity designated by one of them or by the Member State, as data holder, shall grant public and free of charge access to data specified in point 4.2.2 of the Annex regarding connection times between access nodes. Access shall be granted at least via the national access points in accordance with the specifications and access conditions set out in the Annex. 3.   Where a passenger railway undertaking, or where relevant the data holder, has rights or obligations deriving from contractual provisions to grant access to its tariff data that access shall be granted to all its tariffs at least via the national access points in accordance with the specifications and access conditions set out in point 4.3 of the Annex. Additional terms and conditions for direct access to and commercial use of that data may be agreed on a contractual basis. 4.   Where a distributor has rights or obligations deriving from contractual provisions to access availability and reservation data of the rail products of a passenger railway undertaking, including for yielded prices, that access shall be granted by that railway undertaking at least through a direct connection to its attributing system in accordance with the specifications set out in point 4.5 of the Annex. Additional terms and conditions for direct access to and use of that data shall be agreed on a contractual basis. 5.   This Article shall apply in addition to the obligations set out in Article 4.

Cybersecurity and data format

Article 7

1.   Telematics stakeholders, Union bodies and public sector bodies involved in the implementation of this Regulation shall be identified through a single identifier of their organisation assigned and validated in accordance with Article 9. 2.   Where a telematics stakeholder shares and grants access to data pursuant to this Regulation, it shall ensure that the communication networks and protocols, systems, interfaces or databases it uses comply with the cybersecurity measures set out in point 1.3 of the Annex. 3.   Where a telematics stakeholder shares and grants access to data pursuant to this Regulation, it shall comply with the semantics specified in the data catalogue elements as subsets of the ERA Ontology and the data sequence referred to in point 1.4 of the Annex. 4.   The Agency shall ensure that the ERA Ontology and associated specific data catalogue elements reflect regulatory and technical developments affecting the Union rail system.

Common central repository and reference data

Article 8

1.   The Agency shall maintain a common central repository as a single source of common Union rail data for telematics. The repository shall be made available to the public and shall store all the following information: (a) metadata and associated specific data catalogue elements, that are referred to in point 1.4 of the Annex as a subset of the ERA Ontology, specifying the content and the structure of the data; (b) a list of certification authorities for public key infrastructure (‘PKI’) established in accordance with the requirements set out in point 1.3 of the Annex; (c) common reference data, referred to in Article 9, managed by the Agency; (d) a link to access the source of freight specific reference data, referred to in point 3.3 of the Annex, managed by the rail sector. 2.   The Agency shall enable any telematics stakeholder to subscribe to automated notifications regarding any update to the information associated with the common central repository. 3.   A telematics stakeholder may replicate for its own operational use the data available in the common central repository. 4.   The Agency and each telematics stakeholder responsible for common reference data in accordance with points 1.2, and 4.8 of the Annex shall take the following steps: (a) make publicly available and free of charge their reference data for reuse in accordance with the specifications and access conditions set out in the Annex, as well as the service level conditions applied to the availability and accessibility of corresponding repository; (b) manage assignment, maintenance and storage of, and access to, their reference data in a transparent, fair, reasonable, and non-discriminatory manner.

Governance of common reference data

Article 9

1.   The Agency shall provide telematics stakeholders with web applications to allow them to submit requests for the assignment of codes and the updating of associated data elements. The Agency shall define and publish a user manual describing the different functions of the web applications. 2.   The Agency shall define, publish and apply the procedures for managing requests to assign codes and update of associated data elements, including associated language arrangements in accordance with Article 74 of Regulation (EU) 2016/796 and deadlines. That manual shall provide guidance to telematics stakeholders for the submission of requests. 3.   The Agency shall manage and assign common reference data in the form of single reference identifiers (‘codes’), used or intended to be used by telematics stakeholders in respect of the processes referred to in Article 2 (1) to identify the following data elements: (a) entities (‘organisation codes’) involved in data sharing in accordance with acts adopted pursuant to Directive (EU) 2016/797 or Directive (EU) 2016/798 or Directive 2012/34/EU, referred to in point 1.2.1 of the Annex; (b) geographical points (‘location codes’) referred to in point 1.2.2 of the Annex; (c) ticketing aspects (‘code lists for ticketing’) referred to in point 4.8 of the Annex. 4.   A telematics stakeholder shall submit to the Agency requests for the assignment of codes. The request shall be in accordance with the specifications for common reference data set out in point 1.2 of the Annex. 5.   Where a telematics stakeholder submits a request for the assignment of a code for a location in the Union that is outside of the scope of the Union’s rail network referred to in Annex I, point 1, of Directive (EU) 2016/797, the Agency shall assign a location code as a virtual extension of the rail network (‘virtual location code’) in the following cases: (a) where the location is used by transport services that replace rail transport services temporarily; (b) where the location is used by transport services sold as rail transport services that are not operated by railway undertakings; (c) where the location is considered a meta station. 6.   The Agency shall ensure that the position of the location codes assigned is specified in relation to the relevant infrastructure data available in the register of the railway infrastructure (the ‘RINF’) referred to in Article 49 of Directive (EU) 2016/797 and store them. 7.   By 2 September 2026, each infrastructure manager and each operator of rail freight service facilities, or another competent entity established in the Union designated by either, shall specify the position of the location codes, assigned to them before the entry into force of this Regulation, relative to the relevant infrastructure data available in the RINF. 8.   Where, for passenger rail transport services, a telematics stakeholder refers to an access node or a data holder via national access points, it shall use the common reference data managed and assigned by the Agency pursuant this Article as European identifiers (‘EU-Ids’).

Data quality

Article 10

1.   The Agency and each telematics stakeholder shall ensure that their reference data comply with the data quality criteria and nominal values set out in point 1.5 of the Annex and meet an appropriate level of integrity and reliability. 2.   Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall ensure that that data meets an appropriate level of integrity and reliability and contains the reference data referred to in paragraph 1. It shall also endeavour to comply with the nominal values set out in point 1.5 of the Annex with a margin of tolerance of 5% for each of the data quality criteria set out in that point. 3.   Each telematics stakeholder shall ensure that data replicated from the common central repository preserves the same quality level. 4.   Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall perform quality assurance checks. Any deficiencies identified in the data quality shall be corrected as soon as possible. 5.   Each telematics stakeholder shall establish processes for recurrent quality assurance checks against each of the data quality criteria, for at least a selection of routes and locations of reference.

Network-specific data requirements

Article 11

1.   The Agency shall establish and publish a template to collect non harmonised data requirements applied or intended to be applied by telematics stakeholders, as part of the change control management procedure referred to in Article 12(1). 2.   By 2 December 2026, each infrastructure manager shall share with the Agency, as part of the change control management procedure referred to in Article 12(1), the network-specific data requirements it applies or intends to apply and a justification thereof using the template referred to in paragraph 1. Each Member State shall ensure that infrastructure managers under its responsibility comply with the provisions set out in the first subparagraph. 3.   As part of the change control management procedure referred to in Article 12(1) of this Regulation and based on the information collected, the Agency shall, where justified, update the corresponding harmonised specifications referenced in Appendix C of the Annex to this Regulation or recommend to the Commission, pursuant to Article 4(a) of Regulation (EU) 2016/796, the integration of specific cases as part of Section 5 of the Annex to this Regulation. 4.   Telematics stakeholders shall only apply data requirements that are harmonised pursuant to this Regulation or listed as a specific case.

Updates to referenced specifications

Article 12

1.   The Agency shall establish, publish and apply a change control management procedure to update and maintain the harmonised specifications referenced in Appendix C of the Annex. 2.   Where the Agency issues opinions pursuant to Article 10, paragraphs 2 and 3, or Article 19(1), point (d), of Regulation (EU) 2016/796 identifying changes constituting acceptable means of compliance, it shall, where relevant, propose implementation dates for their application. 3.   The Agency shall keep Member States informed of its activities pursuant to paragraph 2 of this Article through the committee referred to in Article 51(1) of Directive (EU) 2016/797.

Lead railway undertaking

Article 13

1.   Where a direct rail transport service is operated or intended to be operated by several railway undertakings, those undertakings shall designate one of them, or another competent entity established in the Union, to be a lead railway undertaking, for the entire service for the following tasks that are part of the processes referred to in Article 2(1): (a) integrating consistently the identification number of the train (‘reference train identifier’) with other object identifiers in accordance with the specifications set out in point 2.1 of the Annex; (b) coordinating the railway undertakings and other applicants involved in relation to capacity management in accordance with the specifications set out in point 2.3 of the Annex; (c) aggregating passenger timetable data for that service, in accordance with the specifications set out in point 4.2 of the Annex, where it differs from the working timetable; (d) monitoring the movement of freight wagons and their load, in accordance with the specifications set out in point 3.2 of the Annex; (e) integrating and sharing consignment note data in case of a freight service and act as a single point of contact for that service, in accordance with the specifications set out in point 3.1.1 of the Annex. 2.   The railway undertakings referred to in paragraph 1 may distribute the tasks referred to in paragraph 1 or part of them to more than one undertaking or competent entity, each acting as the lead railway undertaking in relation to one or more tasks it is responsible for. 3.   Where a direct rail transport service, with or without intermediate stops, is operated or intended to be operated by a single railway undertaking, that undertaking shall be the lead railway undertaking. 4.   A lead railway undertaking responsible for the tasks referred to in paragraph 1, shall act as single point of contact for ensuring the consistency and the integration of the data that is shared or made accessible pursuant to this Regulation by the relevant data holders.

Telematics applications for data sharing

Article 14

1.   Where a telematics stakeholder shares or grants access to data pursuant to this Regulation, it shall use a telematics application. That application shall be based on an application programming interface (‘API’) for machine-to-machine data sharing or a web user interface (‘web UI’) for human-to-machine data sharing which access is provided for use by another telematics stakeholder as an alternative. 2.   Each telematics stakeholder shall ensure that the telematics applications it uses or to which it provides access for use comply with the specifications set out in point 1.7 of the Annex and ensures non-discriminatory data sharing. 3.   Two or more telematics stakeholders may jointly use or jointly provide access for use to one telematics application. 4.   In the areas of capacity management, train preparation and traffic management, each infrastructure manager shall both use an API and provide access for use to web UIs for its network as part of the minimum access package laid down in point 1 of Annex II to Directive 2012/34/EU. Where there is more than one infrastructure manager in a Member State, that Member State may require those infrastructure managers to jointly use such an API and jointly provide access for use to web UIs for their networks. In that case, the Member State concerned shall appoint one infrastructure manager responsible for the joint deployment of those telematics applications. The API and web UIs referred to in the first subparagraph of this paragraph may also be the common Union applications required for multi-network processes pursuant to paragraph 5. 5.   For multi-network processes in the areas of capacity management, train preparation and traffic management: (a) infrastructure managers shall jointly use a common Union API and jointly provide access for use to common Union web UIs; (b) operators of rail freight service facilities may jointly use a common Union API and jointly provide access for use to common Union web UIs. 6.   In the area of the management of freight wagons and their load, freight railway undertakings may jointly use a common Union API and provide access for use to common Union web UIs.

Connection time and passenger information in stations

Article 15

1.   Each station manager, or where relevant the infrastructure manager or another entity designated by one of them, or by the Member State, as the data holder, shall, for the stations under its responsibility, establish in a neutral and non-discriminatory manner, the following minimum connection times in accordance with the requirements set out in point 4.2.2.1 of the Annex and where relevant in cooperation with other station or infrastructure managers: (a) the minimum connection time between access nodes of: (i) different passenger rail transport services within the station; (ii) different passenger rail transport services of different stations that are part of the same meta station; (iii) different passenger rail transport services and other relevant scheduled passenger transport services that may be connected; (b) the minimum connection times referred to in point (a) adapted to: (i) persons with disabilities and persons with reduced mobility; (ii) a passenger transporting a bicycle. 2.   Each station manager, or where relevant the infrastructure manager or the data holder, shall, for the stations under its responsibility, define the applicable means to connect transport services and gather information on the additional time that may be requested as part of the conditions of carriage by a railway undertaking or public authorities for the check-in of passengers, bicycles, or luggage, and include the information thereof in the minimum connection time. 3.   Each station manager, or where relevant the infrastructure manager or the data holder, shall, for the stations under its responsibility, establish in a neutral and non-discriminatory manner, the most appropriate information system to be installed in the station to provide integrated train traffic and train composition rail passenger information in the station area in accordance with the requirements set out in point 4.7.1 of the Annex. 4.   For the purposes of paragraphs 1, 2 and 3 of this Article, passenger railway undertakings, passenger organisations, station managers, infrastructure managers and, where appropriate, the competent authority as defined in Article 2, point (b), of Regulation (EC) No 1370/2007, or where relevant the data holder, shall cooperate with a station manager, or where relevant an infrastructure manager or the data holder, upon request of any of the latter three.

Back to Commission Implementing Regulation (EU) 2026/253 — full text

Articles on this page are reproduced verbatim from official open data. See the attribution line.

Source: EUR-Lex (Publications Office of the EU), © European Union, reuse permitted under Commission Decision 2011/833/EU.

What to look at next