Part of our mission statement is to share our data with anyone who wants it, for free. This page lists all our timetables, and stop place data dumps which are updated daily. All data dumps have permanent URL's and come as NeTEx or GTFS datasets. NeTEx is the official format for public transport data in Norway and is the most complete in terms of available data. GTFS is a downstream format with only a limited subset of the total data, but we generate datasets for it anyway since GTFS can be easier to use and has a wider distribution among international public transport solutions. GTFS sets come in "extended" and "basic" versions.
Please be aware that certain information, important to journey planning, may be lacking in the GTFS files. This is, in particular, true for text-based information, which is not supported by GTFS.
Category: National journey planning. License: NLOD
The stops referred to are defined in the national stop registry. It's possible to log in with the "guest"/"guest"-account to view the content or use the geocoder, or NeTEx dump to extract what you may be looking for.
The stop identifiers are unique across all the datasets. Regardless of the data source.
The richness of the data depends on the source data from the respective county or operator. All parties are required to submit their data in the NeTEx format, in accordance with the Norwegian NeTEX profile, but unfortunately, we're not there yet.
NeTEx and Norwegian profile.
NeTEx (Network and Timetable Exchange) is an XML-based format for sharing public transport data. It is a CEN-standard and is slated to become an EU standard for national datasets.
* GTFS basic does not use extended route types. ** Despite a number of counties being merged in 2020 the affected datasets continue to be delivered separately. *** Parts of northern Trøndelag missing. **** Tertitten, Setesdalsbanen, Thamshavnbanen, Krøderbanen, Gamle Vossebanen.
Whenever new data is uploaded by a data owner an update of the relevant dataset and the national dataset is triggered.
Excessive downloading of files may lead to your IP being blocked. We expect that most users will have no need for more than one download per 24 hours.
Additionally, all datasets are automatically re-validated and re-exported every night where expired data is trimmed away, retaining data for a maximum of 48 hours back in time. The original creation date, and subsequently the date of the most recent change can be found by checking the created timestamp in CompositeFrame. For example: created="2019-05-29T12:59:32.202".
Stops and Quays
Complete datasets for Norway
These datasets are updated every night.
Entire Norway (Current stops) - Latest valid version of all stops in Norway
Entire Norway (Current + future stops) - Current+ future versions of all stops in Norway
Entire Norway (All stop versions, incl. outdated) - Current, future and outdated versions of all stops in Norway
Stops and Quays per region – Current stops
Møre og Romsdal
Troms og Finnmark
Vestfold og Telemark
Railway stations only
Status of NeTEx completeness from providers
All Norwegian PTA's are sending native NeTEx from their planning system. The railway companies and some commercial PTO's are doing the same, while some are still developing this capability. The minor PTO's with only one or two lines are using AddTransit (GTFS) or the Entur-built tool Nplan (NeTEx).
Planning systems in use by Entur customers capable of exporting Nordic NeTEx profile compliant data: