All Norwegian rail (Entur) train delays, Friday 23 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

80% of stops were reached less than 5 minutes late, and half of them within 1 minute of the timetable.

Trains
1,941
5 min late or more
20% of stops
15 min late or more
7% of stops
Median delay
1 min
Cancelled trains
7

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 21,658 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 161 placeholder values the feed sent instead of a time (a train “here, now” hours late, or one time repeated at every stop). 99% of the stops of the trains that ran (skipped stops aside) had a delay.

The archive saw 1,935 of the 2,014 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-BergenÅl stasjon302.6 min
F4 Oslo S-BergenGeilo stasjon263.3 min
F4 Oslo S-BergenArna stasjon83.6 min
RE10 Drammen-Oslo S-LillehammerOslo S75.3 min
F4 Oslo S-BergenOslo S75.3 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-23.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:28-0.1scheduled
Drammen stasjonFLY120:1810.6scheduled
Stavanger stasjonL5 Jærbanen16:300.4scheduled
Åndalsnes stasjonR65 Raumabanen21:436.2scheduled
Stabekk stasjonR21 Stabekk-Oslo S-Moss06:523scheduled
Oslo SR23 Stabekk-Oslo S-Moss10:19-0.7scheduled
Bergen stasjonR40 Bergen-Voss-Myrdal-Ål10:45-0.6scheduled
Lillestrøm stasjonL1 Spikkestad-Oslo S-Lillestrøm21:250scheduled
Bergen stasjonL4 Bergen-Arna09:040.1scheduled
Stabekk stasjonL2 Stabekk-Oslo S-Ski08:044.4scheduled
Oslo SL2 Stabekk-Oslo S-Ski19:590scheduled
Eidsvoll stasjonRE11 Eidsvoll-Oslo S-Skien14:590.2scheduled
Tønsberg stasjonRE11 Eidsvoll-Oslo S-Skien09:41-8.1scheduled
Stokke stasjonRE11 Eidsvoll-Oslo S-Skien19:06-17.3scheduled
Stokke stasjonRE11 Eidsvoll-Oslo S-Skien06:000.3scheduled

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.