Real-Time Data

These APIs allows your server to subscribe to real-time data from all included real-time feeds in Norway on SIRI 2.0. It is available as standard SIRI XML and as SIRI Lite (REST).

These services will include only the realtime-data, and will have to be combined with the plan-data on your server before presented to an end-user. For clients creating an end-user service, the JourneyPlanner API is almost always a better option.


SIRI is a CEN Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.

ET – Estimated Timetable

Real-time estimates for each service journey. Included are planned, actual and estimated departure times, cancellation and changes in stop patterns.

VM – Vehicle Monitoring

Vehicle-centric real-time data with the position of a vehicle, as well as any deviation from scheduled timetable on a given departure.

SX – Situation Exchange

Textual messages displayed to end users. They are always associated with a departure, line, stop etc., or combinations of these.

More information

SIRI standard:

Norwegian SIRI-profile:

Example SIRI-XML that follow the Norwegian SIRI-profile:

Available sources

Entire NorwayYesYesYes
AKTAust- og Vest-Agder (AKT)YesYes
ATBTrøndelag (AtB)YesYes
BRABuskerud (Brakar)YesYes
FINFinnmark (Snelandia)
HEDHedmark (Hedmark Trafikk)Yes
KOLRogaland (Kolumbus)YesYes
MORMøre og Romsdal (Fram)(Yes)(Yes)
NORNordland fylkeskommuneYesYes
BNRVy/Flytoget/Go-Ahead (via Bane NOR)Yes
OPPOppland (Opplandstrafikk)Yes
RUTAkershus & Oslo (Ruter)YesYesYes
SOFSogn og Fjordane (Kringom)
SKYHordaland (Skyss)YesYes
TELTelemark (Farte)
TROTroms (Troms fylkestrafikk)YesYes
VKTVestfold (VKT)
OSTØstfold (Østfold kollektivtrafikk)YesYesYes

Delta load/changes


When using publish/subscribe you'll first get one (or more) set with initial data, and then continuous updates with changes. This option requires an accessible endpoint which accepts HTTP POST requests from the Entur SIRI service.


For Request/Response, the <RequestorRef> attribute is used to track changes and must therefore remain the same for all subsequent requests in order to only get changes. The attribute MoreData=true means the data comes in bunches, just like paging, and more data can be fetched immediately after the first "page" is received. Eg. if there are 20,000 objects, these will be split up in smaller parts and repeated requests are needed to get the full set.


With simple HTTP GET calls to retrieve data, you can use the ´requestorId´ URL-parameter to only retrieve changes made since the last time you asked. If you do not use this, you will always get the full dataset, not just the first time you make a request. You must use a unique UUID.