Renfe long and medium distance train delays, Monday 9 November 2026

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

How late the trains were

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

Trains
1,099
5 min late or more
58% of stops
15 min late or more
30% of stops
Median delay
7 min
Cancelled trains
73

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 9,788 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 4 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,070 of the 1,289 trains the timetable planned for this day.

Not counted in the trains planned: 286 more trains the timetable lists on lines the live feed has not carried in the week before (RENFE OPERADORA).

Most delayed trains

LineLeft its first stopWhere it was latestDelay
MDAraia269 min
REG.EXP.Mérida113 min
AVLOVigo Urzaiz97 min
REG.EXP.Torrijos93 min
IntercityVitoria-Gasteiz83 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=es-renfe-ld/service=TripUpdate/date=2026-11-09.parquet?token=YOUR_TOKEN

Examples for this day Try it in your browser

A few rows of the file

14 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
BadajozALVIA13:4911scheduled
CartagenaIntercity20:4612scheduled
Madrid-Chamartín-Clara CampoamorIntercity10:398scheduled
Segovia-GuiomarALVIA16:5114scheduled
Castelló de la PlanaAVE12:534scheduled
Sevilla-Santa JustaAVANT07:09-3scheduled
Vigo-GuixarREGIONAL18:224scheduled
Villarrubia de CórdobaPROXIMDAD08:214scheduled
Albacete-Los LlanosMD16:1611scheduled
Lleida-PirineusREG.EXP.18:2020scheduled
HuescaREGIONAL15:346scheduled
SegoviaREGIONAL20:214scheduled
Barcelona Estació de FrançaREG.EXP.10:4450scheduled
Salamanca-La AlamedillaMD14:0710scheduled

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.