ETCS
ETCS is in operation on roughly a tenth of the TEN-T network. The target architecture is settled; what governs delivery now is how quickly each line can be planned, tested and approved. Programmes that industrialise those steps deliver each line faster than the last.

This is the train control layer - the rules that govern how a line is planned and operated, the data models those rules operate on, and the track and vehicle systems that implement the ERTMS subsets. For the interlocking, see Digital Interlockings.
The state of ETCS deployment
By the end of 2024, ETCS was only in service on some 12,400 km of the TEN-T network, around a tenth of it, with roughly a fifth of the EU fleet fitted. Belgium completed deployment across its national network in December 2025, the first sizeable member state to do so (second overall after Luxembourg). The European Commission's third ERTMS work plan, published in February 2026, records real progress and calls for acceleration.
The gap between plan and delivery is not primarily technological. Deployment rates are set by testing capacity, integration effort, particularly with existing infrastructure and neighbouring interlockings, approval throughput and the availability of fitted vehicles and track access. Transnational corridors exacerbate these challenges, with special planning and system integration efforts often needed in the border areas.
The counter-strategy is standardisation and repeatability: generic engineering rules instead of per-line design, planning data in a form that tools can check, and approval evidence produced the same way each time, e.g. through model checking. Every avoidable exception adds complexity, risk and duration to a programme that is already measured in decades.
ETCS on the TEN-T Core Network, by member state
Explore the latest data from the ERTMS Work Plan.
of the EU TEN-T Core Network was in service with ETCS at the end of 2024 - 10,584 km of 63,959 km
is in operation or already under contract - 23,913 km, more than twice what is running
is planned to be equipped by 2030, against a TEN-T Regulation deadline of 100%
"Contracted" is the Commission’s in-operation-plus-under-construction column: it defines a section as under construction once a supplier has been contracted, and does not separate the two.
Non-EU TEN-T participants, contribution to TEN-T corridors only.
Figures are end-2024, from Annex II of the 2026 ERTMS Work Plan - the only source covering every member state on one denominator, which is why it is used here rather than the infrastructure managers’ own announcements, which mix route and track kilometres and different network subsets. The ETCS variant split is not published per member state; where an infrastructure manager publishes its own, it is in the table. ERTMS Work Plan 2026, Annex II - deployment status per member state
What decides how fast a line is equipped
Deployment rate is set by planning, testing and approval throughput. These are the areas we work in.

Generic rules instead of per-line design
Operational rules, engineering/planning guidelines and technical specifications have to be consistent in themselves and across borders, better yet harmonised across Europe. EU Rail initiatives provide a framework for this harmonisation but planning is still often done within a very narrow project scope or differs from region to region, leading to inefficiencies and special treatment for every rollout. Nationally independent engineering rules for ETCS Level 2 Full Supervision without lineside signals allow one ruleset to serve a corridor rather than a single network while offering opportunities for simplification. We develop such rules with infrastructure managers and within Europe's Rail, including the requirements they place on the safety logic.
- Complexity reduction
- Operations, planning and safety logic requirements
- Harmonisation and standardisation
Planning data that tools can read
Rules are only as automatable as the data they operate on. Extending the EU-Rail System Pillar's Conceptual Data Model or adopting standards such as IFC or railML during planning and at configuration time lets plans move between tools as data rather than as drawings, which is the precondition for checking them mechanically at all.
- Data modelling
- Pre-processing of planning artefacts
- Configuration assistance including operational data, technical configuration and networking
Tool support
Rules written and modelled formally are unambiguous to read and executable to check. T2 tooling for verification or T3 tools for automated generation; tooling built on such formalised rules can save time and effort by handling the mechanical aspects - completeness, consistency, rule compliance across thousands of objects.
- Rulesets formalised for unambiguous interpretation
- Semi-automated checking of new and existing plans and configurations
- Findings presented for assessment by qualified personnel where required

RBC modelling, system development and integration
The ETCS trackside systems not only have to satisfy TSI CCS requirements and prove interoperability with onboard systems, they also have to work with the interlocking, neighbouring RBCs and the operational systems around them such as diagnostic, network and security services. Modelling the RBC and its neighbours gives a testable representation of that behaviour before the real components are available and can solidify integration contracts. A distributed test laboratory lets teams in different locations work against one shared setup and makes holistic lab-side system testing viable before expensive ESC (ERTMS System Compatibility) tests, test drives and other field tests are executed. Integration evidence then arrives earlier, and arrives the same way each time it is needed.
- MBSE for ETCS subsystems including formal verification
- Distributed test laboratories shared across sites and partners
- Repeatable automated integration and regression testing
- Software development and configuration for integration into neighbouring systems
Optimising the commissioning process
Commissioning ETCS trackside systems is complex and involves multiple stakeholders. By simulating the RBC and its interactions with interlockings and operational systems, we can identify potential issues early and streamline the commissioning process. This reduces downtime and ensures a smoother rollout of new infrastructure.
- Early identification of potential process bottlenecks
- Consultation on optimisation and automation potential
- Reduced blocking time and closure periods and smoother infrastructure rollout
Services
What we deliver on these projects, for infrastructure managers and for suppliers.
Requirements management
Specification work from operational context through system requirements specification to implementation. For planning guidelines, software and data.
Read the case studyDevelopment Support
Modelling and development of RBC data and logic and the interfaces around it both for ERTMS subsets as well as integrations to EULYNX or NeuPro interlockings (SCI-ILS).
Book a free consultationIntegration Testing
Test environments covering ETCS trackside and the systems around it. We partner for ETCS OBU Simulations and testing.
Discover Platform21Deployment Support
Assistance with the deployment of ETCS systems, ensuring smooth integration and operation within existing infrastructure.
Looks useful to you?
Get in touch with us to discuss how our products can enhance your capabilities best.
- Experts in Rail
- Traditionally Reliable
- Natively Digital