All Norwegian rail (Entur) train delays, Friday 30 October 2026

Delays recorded on this day, in Norway local time. Below: how it went, then the whole day as one file to download.

How late the trains were

89% of stops were reached less than 5 minutes late, and half of them within 0.8 minutes of the timetable.

Trains
1,917
5 min late or more
11% of stops
15 min late or more
2% of stops
Median delay
0.8 min
Cancelled trains
1

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 21,670 stops that had one, as the operator sent it. Cancelled trains (marked cancelled, or with every stop skipped), skipped stops and values over an hour early or twelve hours late are left out, as are 60 placeholder values the feed sent instead of a time (a train “here, now” hours late, or one time repeated at every stop). 100% of the stops of the trains that ran (skipped stops aside) had a delay.

The archive saw 1,919 of the 2,002 trains the timetable planned for this day.

Not counted in the trains planned: 95 more trains the timetable lists on lines the live feed has not carried in the week before (Öresundståg, Snälltåget, SJ).

Most delayed trains

LineLeft its first stopWhere it was latestDelay
F4 Oslo S-BergenGeilo stasjon157 min
R60 RørosbanenStøren stasjon142.2 min
R13 Drammen-Oslo S-DalDrammen stasjon137 min
F5 Sørtoget regionMoi stasjon121.6 min
F4 Oslo S-BergenHokksund stasjon115.7 min

Download

Read this day from code

This day’s table of final delays has a fixed address. Read it from DuckDB, Polars or curl, with one of your API tokens in place of YOUR_TOKEN:

https://data.train-archive.eu/daily/provider=no-entur/service=TripUpdate/date=2026-10-30.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

15 different trains, each at one stop. The CSV has more columns, listed below.

Stop stop_nameLine routeArrival predicted_arrivalDelay (min) arrival_delay_minStatus trip_status
Oslo lufthavn stasjonFLY206:290.1scheduled
Drammen stasjonFLY119:502scheduled
Egersund stasjonL5 Jærbanen15:351.2scheduled
Åndalsnes stasjonR65 Raumabanen13:300scheduled
Oslo SRE20 Oslo S-Halden-Göteborg (X-Border)08:422.3scheduled
Oslo SRE20 Oslo S-Halden-Göteborg (X-Border)09:080.6scheduled
Dal stasjonR13 Drammen-Oslo S-Dal00:114.6scheduled
Asker stasjonL1 Spikkestad-Oslo S-Lillestrøm16:354.6scheduled
Notodden stasjonR55 Porsgrunn-Notodden08:47-2.8scheduled
Arna stasjonL4 Bergen-Arna23:03-0.9scheduled
Ski stasjonL2 Stabekk-Oslo S-Ski15:071.1scheduled
Bergen stasjonF4 Oslo S-Bergen13:08-3.7scheduled
Tønsberg stasjonRE11 Eidsvoll-Oslo S-Skien09:106scheduled
Tønsberg stasjonRE11 Eidsvoll-Oslo S-Skien17:40-9scheduled
Stokke stasjonRE11 Eidsvoll-Oslo S-Skien06:42-1.8scheduled

What the columns mean

service_date
The day the train was scheduled to run.
route
The line, as the operator names it (for example IC 3 or S2).
trip_id
The operator’s code for this train run. The same train on another day has another code.
trip_start_time
When the train was scheduled to leave its first station.
stop_sequence, stop_id, stop_name
Which stop along the route: its position, code and name.
arrival_delay_min, departure_delay_min
How late the train was at that stop, in minutes. Negative means early. Empty when the operator gave a time but no delay.
predicted_arrival, predicted_departure
The time the operator last announced for that stop, in local time.
observed_at
When that last announcement was seen. After the train has passed, it is what happened.
trip_status
scheduled, cancelled or added (a train that was not in the timetable).
stop_status
skipped when the train did not stop there; empty otherwise.
route_id
The route’s code in the timetable, to join with it.