FGV: Metrovalencia lines 1 and 2 train delays, Monday 26 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

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

Trains
270
5 min late or more
32% of stops
15 min late or more
1% of stops
Median delay
3 min
Cancelled trains
0

Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 7,116 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 12 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 270 of the 298 trains the timetable planned for this day.

Not counted in the trains planned: 7 more trains the timetable lists on lines the live feed has not carried in the week before (Metro Valencia).

Most delayed trains

LineLeft its first stopWhere it was latestDelay
1 1 - Castelló - Seminari - CEUMassarrojos20 min
2 2 - València Sud - Torrent AvingudaPicanya20 min
1 1 - Picassent - València SudValència Sud19 min
2 2 - Llíria - València SudPl. Espanya19 min
2 2 - Llíria - Torrent AvingudaTorrent Avinguda19 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-fgv-valencia/service=TripUpdate/date=2026-10-26.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
València Sud2 2 - Torrent Avinguda - València Sud23:134scheduled
Llíria2 2 - Torrent Avinguda - Llíria19:024scheduled
Llíria2 2 - Torrent Avinguda - Llíria14:505scheduled
Paterna2 2 - Torrent Avinguda - Paterna09:144scheduled
Seminari - CEU1 1 - Castelló - Seminari - CEU22:253scheduled
Seminari - CEU1 1 - València Sud - Seminari - CEU13:493scheduled
Seminari - CEU1 1 - València Sud - Seminari - CEU05:551scheduled
Torrent Avinguda2 2 - Llíria - Torrent Avinguda19:298scheduled
Torrent Avinguda2 2 - Llíria - Torrent Avinguda14:598scheduled
Torrent Avinguda2 2 - Paterna - Torrent Avinguda10:104scheduled
Picanya2 2 - València Sud - Torrent Avinguda05:5120scheduled
Torrent1 1 - Bétera - Torrent19:339scheduled
Castelló1 1 - Bétera - Castelló15:4414scheduled
Torrent1 1 - Bétera - Torrent09:412scheduled
Castelló1 1 - Empalme - Castelló06:298scheduled

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.