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

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

Trains
1,715
5 min late or more
10% of stops
15 min late or more
2% of stops
Median delay
0.7 min
Cancelled trains
6

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 18,096 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 6 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,710 of the 1,790 trains the timetable planned for this day.

Not counted in the trains planned: 94 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
RX11 Eidsvoll-Oslo S-SkienAsker stasjon60.8 min
RE20 Oslo S-Halden-Göteborg (X-Border)Ed station56 min
F5 Sørtoget regionLysaker stasjon54.2 min
RE20 Oslo S-Halden-Göteborg (X-Border)Göteborg Centralstation49 min
F4 Oslo S-BergenVikersund bussterminal46.2 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-14.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
Oslo lufthavn stasjonFLY116:01-0.1scheduled
Stavanger stasjonL5 Jærbanen09:000scheduled
Stavanger stasjonL5 Jærbanen19:451.6scheduled
Bodø stasjonF7 Nordlandsbanen21:1312.4scheduled
Oslo SRE30 Oslo S-Gjøvik17:30-1.2scheduled
Bergen stasjonR40 Bergen-Voss-Myrdal-Ål14:14-0.9scheduled
Lillestrøm stasjonL1 Spikkestad-Oslo S-Lillestrøm09:478scheduled
Bergen stasjonL4 Bergen-Arna17:33-0.2scheduled
Ski stasjonL2 Stabekk-Oslo S-Ski18:48-2.9scheduled
Eidsvoll stasjonR12 Kongsberg-Oslo S-Eidsvoll10:323.3scheduled
Oslo S TrelastgataR22 Skøyen-Oslo S-Mysen-Rakkestad05:52-55.8scheduled
Asker stasjonRE11 Eidsvoll-Oslo S-Skien12:14-6.5scheduled
Tønsberg stasjonRE11 Eidsvoll-Oslo S-Skien20:09-10.4scheduled
Stokke stasjonRE11 Eidsvoll-Oslo S-Skien06:440scheduled

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.