Dev:Registers

XML Railway exchange format https://railML.org Latest release: 3.3 SR1 (June 18th 2025)

Quick links Subschemas Infrastructure Interlocking Rollingstock Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes  Dev:Changes/3.2 Dev:Changes/3.3 Guides Semantic Constraints FAQ

railML® 2 Wiki – RailTopoModel® Wiki

The codelist Registers contains registers, databases, handbooks etc. Your railML^® download may contain the codelist in a directory codelists, next to documentation and schema. As the codelists have shorter cycles than railML^® versions have you might want to get the current list from https://development.railml.org/railml/shared/-/raw/master/codelists/Registers.xml (link to the railML^® website).

The code lists are intended to address certain frequently used entities with a single code, to avoid repetitious work as well as ambiguity errors. Moreover, the separation of schema and codelists allows actualizing the codelists in very short cycles. The concept of codelists is explained in the overview of codelists along with the procedure to extend the list if you are missing an entry.

Structure

The container element is named <registers>.

The items are named <register> with the following specification:

• Attributes
  • code: A code, that should be referred to from within an railML^® file
• Children
  • <name>: Internationalized name of the register
  • <organization>: Organization name that is responsible for the register
  • <remarks>: Internationalized remarks for the register

Example entry

<register code="RL100">
 <name xml:lang="de-DE">Betriebsstellenverzeichnis</name>
 <organization xml:lang="de-DE">DB</organization>
 <remarks xml:lang="de-DE">auch/früher als DS100 oder Ril100 bezeichnet</remarks>
 <remarks xml:lang="en">also/former known as DS100 or Ril100</remarks>
</register>

Affected Elements

railML^® 2

In railML^® 2, the designator can be added to the following elements:

• Infrastructure subschema
  • <impairmentSection>
  • <ocp>
  • <state>
• Common subschema
  • <concessionaire>
  • <contractor>
  • <customer>
  • <infrastructureManager>
  • <operationalUndertaking>
  • <project>.
  • <railwayUndertaking>
  • <vehicleManufacturer>
  • <vehicleOperator>
  • <vehicleOwner>

railML^® 3

In railML^® 3, the <designator> can be added to any type of <functionalInfrastructure> and <assetsForInterlocking> element, e.g. <operationalPoint>, <route>, etc. It is also available for many other elements. Check the Parents section of the <designator> page for your railML^® 3 version for a list of all elements with designator in that version.

Note that the designator element was moved from <CO:designator> in railML^® 3.1 to <Generic:designator> in railML^® 3.2 and later versions.

Current entries

railML® Code	Name	Organization	Remarks	Status	Scope/ambit	URL	Contact
Code/abbreviation of the register	Name of the register	Issuer		eg "proposed" or date of introduction	eg a country or a net for which the register applies	source of the register	Maintainer
BaneData	no:BaneData	no:Bane NOR	en:Infrastructure asset database of Bane NOR		Norway ()	https://oppslagsverk.banenor.no/datakatalogen/ (external link)	https://www.banenor.no/en/customer-service/help-and-contact-information/ (external link)
BaneData-FL	en:BaneData functional location	no:Bane NOR	en:Register of functional locations for infrastructure objects in Bane NOR’s network. A functional location represents the place or area in the network where an object can be installed to perform a specific function.	23.10.2025	Norway ()	https://oppslagsverk.banenor.no/datakatalogen/funksjonell-lokasjon/registrering/ (external link)	https://www.banenor.no/en/customer-service/help-and-contact-information/ (external link)
CZPOD	cz:Česky Prohlášení o Dráze en:Czech Network Statement	cz:Správa železnic, státní organizace	cz: Počet železničních tratí podle přílohy E aktuálního prohlášení o české drahy en: Number of railway line as available in Annex E of current Czech Network Statement	23.03.2025	Czechia ()	https://provoz.spravazeleznic.cz/Portal/ViewArticle.aspx?oid=168 (external link)	One Stop Shop Czechia oss@spravazeleznic.cz Phone: +420 972 244 566
DB640	de-AT: Dienstbehelf Nr. 640	de-AT: ÖBB	Austrian "Dienstbehelf No. 640" of Österreichische Bundesbahnen.		Austria () and some selected stations across Europe
DfA	de-CH: Datenbank Feste Anlagen fr-CH: banque de données des installations fixes it-CH: banca dati degli impianti fissi	de-CH: Schweizerische Bundesbahnen im Auftrag des Bundesamtes für Verkehr fr-CH: Chemins de fer fédéraux suisses par ordre Office fédéral des transports it-CH: Ferrovie Federali Svizzere su incarico Ufficio federale dei trasporti en: Swiss Federal Railways on behalf of Federal Office of Transport	Swiss railway asset database including spatial information.		Switzerland ()		SBB: streckennetz@sbb.ch
DIDOK	de-CH: Liste der Stationsnamen (Dienststellendokumentation) fr-CH: Liste des noms des stations it-CH: Lista dei nomi delle fermate en: List of station names	de-CH: Schweizerische Bundesbahnen im Auftrag des Bundesamtes für Verkehr fr-CH: Chemins de fer fédéraux suisses par ordre Office fédéral des transports it-CH: Ferrovie Federali Svizzere su incarico Ufficio federale dei trasporti en: Swiss Federal Railways on behalf of Federal Office of Transport	Swiss "Dienststellendokumentation (external link)" of Schweizerische Bundesbahnen on behalf of Bundesamt für Verkehr (external link) (Map (external link)). Not to be confused with the Swiss Location Identification (see the SLOID register).		Switzerland () and some stations in border regions	https://data.geo.admin.ch/ch.bav.haltestellen-oev (external link)
DKTPYK	el:Κατάλογος δρομολογιακών θέσεων εκμετάλλευσης Ελλάδας en:Greek Timetable Operational Points Register	el:Οργανισμός Σιδηροδρόμων Ελλάδος (Τμήμα Δρομολογίων/ΤΠΥΚ) en:Hellenic Railways Organization (Traffic Directorate/TPYK)		26.10.2021	Greece ()		OSE, Traffic Directorate, secdk@osenet.gr
DRR-BE	fr-BE: Document de Référence du Réseau nl-BE: Netverklaring	fr-BE: Infrabel nl-BE: Infrabel	fr-BE: courte description et la source nl-BE: korte beschrijving en de bron		Belgium ()
ECVVR	en: European Centralised Virtual Vehicle Register (ECVVR)	en: European Union Agency For Railways	en: The European Centralised Virtual Vehicle Register (ECVVR) is a centralised database that consolidat es vehicle information across Europe.	24.07.2025	See list of available countries at ERA webpage (external link)	https://www.era.europa.eu/domains/registers/ecvvr_en (external link)	ERA: servicedesk@era.europa.eu
ENEE	ENEE Database Station Code	fr: UIC	Station code of ENEE database managed (based on UIC ()/OSJD () Leaflet/IRS 920-2) by UIC. See UIC's download page (external link) for more details.	closed by UIC since June 1st, 2019		https://www.uic.org/location-codes-enee (external link)
ERATV	en: European Register of Authorised Types of Vehicle	en: European Union Agency For Railways	en: ERATV is established according to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community and Commission Implementing Decision 2011/665/EU of 4 October 2011 on the European register of authorised types of railway vehicles.	24.07.2025	European Economic Area () and cooperating countries	https://eratv.era.europa.eu/eratv/ (external link)	ERA: servicedesk@era.europa.eu
GAIA	fr: Gaïa	fr: SNCF Réseau	en: infrastructure register based on ARIANE data model
IBNR	IBNR	de: Europäisches Fahrplanzentrum	Numbers used in some public timetable databases and some customer information systems (EFZ - Europäisches Fahrplanzentrum der DB; Frankfurt/Main). This enumeration entry requires the value to be an integer number.
LVV	nl: Lijst van verkortingen	nl: ProRail / RIGD Loxia	See https://wiki.ovinnederland.nl/wiki/Plaatsnaamverkortingen (external link) for more information		Netherlands ()
NSR	no:Nasjonalt stoppestedsregister en:National Stop Register	no:Entur	en:National Stop Register (NSR) is the master database for public transport stops in Norway (rail and other modes) and is primarily used to store and redistribute detailed information regarding the infrastructure of a stop place.	23.10.2025	Norway ()	https://developer.entur.org/pages-nsr-nsr (external link)	Entur: kollektivdata@entur.org
OCR	en: Organisation Code Register (OCR)	en: European Union Agency For Railways	en: Register of Organisation Codes allocated by ERA to entities operating in the Single European Railway Area and interacting with ERA hosted registers. For companies involved in TAF/TAP data exchange and companies cooperating with OSJD members, ERA will allocate the same Organisation Code as the company's UIC RICS code.	08.09.2025	European Economic Area () and cooperating countries	https://www.era.europa.eu/domains/registers/ocr_en (external link) https://teleref.era.europa.eu/ (external link)	ERA: servicedesk@era.europa.eu
PLC	en: Primary Location Code for the TAF/TAP TSI	en: RailNetEurope for ERA	en: Used for the communication between the railway undertaking and the infrastructure manager. format: country code as ISO-3366-1 + 5 digits		European Economic Area () and cooperating countries	https://rne.eu/it/rne-applications/ccs/crd/ (external link) https://teleref.era.europa.eu/ (external link)	RNE: support.ccs@rne.eu
RICS	en: Railway Interchange Coding System (RICS)	en: International union of railways (UIC) fr: Union Internationale des Chemins de fer (UIC)	en: 4 digit codes used in various applications to identify a company involved in the railway business		Global	https://uic.org/support-activities/it/rics (external link)	UIC: oca@uic.org
RL100	de-DE: Betriebsstellenverzeichnis	de-DE: DB Netz	de-DE: auch/früher als DS100 oder Ril100 bezeichnet en: also/former known as DS100 or Ril100 German "Betriebsstellenkürzel", Dienstvorschrift/Richtlinie No. 100 of Deutsche Bahn.		Germany () and some selected stations across Europe		DB Netz AG; Department I.NBF 31 (Policy and Competency Management)
SJN	no: Strekningsbeskrivelse for jernbanenettet	Bane NOR	"Route description for the rail network" for the Norwegian rail network owned by Bane NOR, including location codes (external link)	12.03.2018	Norway ()	https://orv.banenor.no/sjn (external link)
SLC	en: Subsidiary Location Code for the TAF/TAP TSI	en: RailNetEurope for ERA	en: Used for the communication between the railway undertakings where detailed information within a primary location is needed. format: 1 to 10 (1AN – 10AN and special characters based on extended ASCII codes)		European Economic Area () and cooperating countries	https://rne.eu/it/rne-applications/ccs/crd/ (external link)	RNE: support.ccs@rne.eu
SLOID	en: Swiss Location Identification (SLOID)	de-CH: Schweizerische Bundesbahnen im Auftrag des Bundesamtes für Verkehr fr-CH: Chemins de fer fédéraux suisses par ordre Office fédéral des transports it-CH: Ferrovie Federali Svizzere su incarico Ufficio federale dei trasporti en: Swiss Federal Railways on behalf of Federal Office of Transport	Unique identifier of Swiss stop locations (external link). Not to be confused with the DiDok abbreviation (see the DIDOK register).		Switzerland () and some stations in border regions	en: https://opentransportdata.swiss/en/dataset/service-points-actual-date (external link) de-CH: https://opentransportdata.swiss/de/dataset/service-points-actual-date (external link) fr-CH: https://opentransportdata.swiss/fr/dataset/service-points-actual-date (external link) it-CH: https://opentransportdata.swiss/it/dataset/service-points-actual-date (external link)	SBB: atlas@sbb.ch
SR70	cz: Služební rukověť 70	cz: Správa železnic ()	en: Register of locations of SŽ infrastructure in Czech Republic		Czechia ()	https://provoz.spravazeleznic.cz/portal/viewarticle.aspx?oid=34462 (external link)
STNX	en: Station Numbers (STANOX)	Network Rail	STANOX codes are used in the Total Operations Processing System (TOPS), and are supposedly unique siding location numbers.	12.03.2018	Great Britain and Northern Ireland ()
TJN	no: Trafikkregler for jernbanenettet	Bane NOR	"Traffic rules for the rail network" for the Norwegian rail network owned by Bane NOR, including signal definitions (external link)	19.02.2019	Norway ()	https://orv.banenor.no/orv/doku.php?id=TJN (external link)
TPLC	en: Timing Point Location (TIPLOC)	Network Rail	TIPLOCs are used by train planners to identify what time trains should arrive at, depart or pass a particular point. They are limited to seven characters.	12.03.2018	Great Britain and Northern Ireland ()
UNO	en: Unified Network Objects	de-CH: Schweizerische Bundesbahnen im Auftrag des Bundesamtes für Verkehr fr-CH: Chemins de fer fédéraux suisses par ordre Office fédéral des transports it-CH: Ferrovie Federali Svizzere su incarico Ufficio federale dei trasporti en: Swiss Federal Railways on behalf of Federal Office of Transport	Database of Swiss railway topology elements.		Switzerland ()		SBB: uno@sbb.ch
UOPID	en: UniqueOPID	en: European Union Agency for Railways de-DE: Eisenbahnagentur der Europäischen Union	Code composed of country code and alphanumeric OP code to describe OP in RINF register		European Economic Area () and cooperating countries	https://www.era.europa.eu/domains/registers/rinf_en (external link), Knowledge Base
UUID	en: Universally Unique Identifier	None	As defined by the Internet Engineering Task Force (IETF) in RFC 9562 (external link). See also Universally unique identifier ().		Global

Expansion

The aim of the aforementioned, coordinated collection of registers is to ensure a clear assignment of the corresponding codes. railML.org e.V. can notify these corresponding registers on the assistance of the corresponding international, national or company-specific register owners. railML.org e.V. cannot and will not check the content of the data structures or concrete contents of the registers. In this respect, railML.org e.V. cannot guarantee that the content of the register mentioned is suitable for the purpose of exchange. If you have any questions or requests for changes, please contact the relevant, named register owner. railML.org e.V. will be happy to assist you in making contact. If no suitable register has been named for the purpose, the following options are available:

1. Addition of the register in the railML^® schema
   The corresponding register can be included at short notice, free of charge and without modification of the railML^® schema version, if the register is generally applicable and in practical use and maintenance by the registry is guaranteed. The further procedure is explained on the dev:Codelists#Missing_entries page.
2. Use of a project-specific independent register
   For internal project purposes, each program/project can also use its own register, which is not included in railML.org e.V.. Please note that this register shall begin with the character "_" in the abbreviation and should not be in external, generally valid practical usage.
   Example:

   <register code="_CRL">
   ...
   </register>

Ziel der vorgenannten, koordinierten Sammlung der Register ist es, eine eindeutige Zuordnung der entsprechenden Codes zu gewährleisten. railML.org e.V. kann dabei auf Zuarbeit der entsprechenden internationalen, nationalen oder firmenspezifischen Registerinhaber diese entsprechenden Register notifizieren. railML.org e.V. kann und wird keine inhaltliche Überprüfung der Datenstrukturen oder konkreten Inhalte der Register durchführen. Dahingehend kann railML.org e.V. auch keine Garantie geben, ob der Inhalt des genannten Registers für den Austauschzweck geeignet ist. Bitte wenden Sie sich bei Fragen oder Änderungswünschen an den entsprechenden, benannten Registerinhaber. railML.org e.V. kann gern bei der Kontaktaufnahme behilflich sein. Sofern für den Einsatzzweck kein geeignetes Register benannt ist, bestehen grundsätzlich folgende Möglichkeiten:

1. Ergänzung des Registers im railML^®-Schema
   Das entsprechende Register kann kurzfristig, kostenfrei und ohne Änderung der railML^®-Schema-Version aufgenommen werden, wenn das Register im Anwendungsbereich allgemeingültig und in Praxisanwendung ist sowie eine Wartung durch die Registerstelle gewährleistet ist. Das weitere Vorgehen ist auf der Seite dev:Codelists#Missing_entries beschrieben.
2. Verwendung eines projektspezifischen unabhängigen Registers
   Für projektinterne Zwecke kann jedes Programm/Projekt auch ein eigenes Register verwenden, welches nicht bei railML.org e.V. aufgenommen wird. Dabei ist darauf zu achten, daß dieses Register in der Abkürzung mit dem Zeichen "_" beginnen muß und eben nicht in externer allgemeingültiger Praxisanwendung sein sollte.
   Beispiel:

   <register code="_MOBA">
   ...
   </register>