The Universal Language of Transit: CEN/TS 16614 (NeTEx) Explained
Master CEN/TS 16614 (NeTEx): The European standard for exchanging public transport data. Learn how it handles complex topology, timetables, and fare structures in XML.

What is CEN/TS 16614?
CEN/TS 16614, commonly referred to by its acronym NeTEx (Network Timetable Exchange), is the European Technical Specification for the exchange of Public Transport data. It defines a standardized XML schema used to transmit static data, such as network topology, scheduled timetables, and complex fare structures, between different computer systems.
While EN 12896 (Transmodel) provides the abstract conceptual model (the “brain”), CEN/TS 16614 provides the physical data format (the “voice”). It allows a bus operator in France to send their schedule to a travel planner in Germany with zero ambiguity. It is the designated standard for data exchange under the EU Delegated Regulation 2017/1926, obliging member states to make transport data available via National Access Points (NAPs).
The Three Pillars of NeTEx
The standard is divided into specific parts to handle the vast complexity of modern transport networks:
- Part 1: Public Transport Network Topology: Defines the physical infrastructure, including stop points, routes, lines, and operational constraints (e.g., “this track is for high-speed trains only”).
- Part 2: Scheduled Timetables: Handles the timing of journeys, vehicle runs, day types (weekdays vs. holidays), and coupling/uncoupling of trains.
- Part 3: Fare Information: This is NeTEx’s strongest feature. Unlike simpler formats, it can model complex pricing rules, such as zone-based fares, time-dependent pricing (peak/off-peak), and special products like monthly passes or student discounts.
Why NeTEx Over Legacy Formats?
Historically, operators used proprietary CSV files or the Google-developed GTFS. While GTFS is excellent for simple route planning (B2C), it lacks the depth required for backend operations and complex interoperability (B2B). CEN/TS 16614 is designed to handle the “nitty-gritty” operational details, such as accessibility for wheelchairs at specific platforms or restrictions on bicycle carriage.
Comparison: CEN/TS 16614 (NeTEx) vs. GTFS
The industry often confuses these two. The table below clarifies their distinct roles in the railway and transport ecosystem.
| Feature | GTFS (General Transit Feed Spec) | CEN/TS 16614 (NeTEx) |
|---|---|---|
| Origin | Industry-led (Google). | Standardization Body (CEN). |
| Primary Use Case | Passenger Journey Planning (B2C). | Data Exchange between Professionals (B2B) & NAPs. |
| Data Model | Simple, flat CSV files. | Rich, hierarchical XML based on Transmodel. |
| Fare Capability | Basic (Flat rates, simple transfers). | Advanced (Complex zones, yield management, profiles). |
| Identifiers | Local (Agency specific). | Global/National (Permanent IDs required). |
Implementation in the EU
Adoption of CEN/TS 16614 is no longer optional for major European corridors. It ensures that cross-border travel applications can function seamlessly. By standardizing how a “journey” is defined, it paves the way for MaaS (Mobility as a Service), allowing a single app to book a train, a metro, and a bike rental in one transaction.





