Renfe long and medium distance train delays, Sunday 11 October 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

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

Trains
934
5 min late or more
44% of stops
15 min late or more
19% of stops
Median delay
3 min
Cancelled trains
15

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 8,809 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 3 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 914 of the 1,093 trains the timetable planned for this day.

Not counted in the trains planned: 142 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
EUROMEDValència-Estació del Nord154 min
EUROMEDValència-Estació del Nord154 min
EUROMEDValència-Estació del Nord154 min
MDAlicante/Alacant-Terminal150 min
MDSant Vicent Centre150 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-10-11.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
BadajozALVIA14:071scheduled
València-Estació del NordIntercity17:05-4scheduled
HuelvaALVIA22:2510scheduled
SantanderALVIA17:43-4scheduled
Madrid-Chamartín-Clara CampoamorAVE19:435scheduled
PuertollanoAVANT18:26-4scheduled
Murcia del CarmenAVANT13:461scheduled
Santiago de Compostela-Daniel CastelaoREGIONAL21:227scheduled
Alcolea de CórdobaPROXIMDAD15:35-3scheduled
CartagenaPROXIMDAD11:171scheduled
Salou-Port AventuraREGIONAL19:03-3scheduled
Pamplona/IruñaREG.EXP.11:2211scheduled
Madrid-Chamartín-Clara CampoamorMD36scheduled
Salamanca-La AlamedillaMD15:460scheduled

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.