FGV: Metrovalencia lines 1 and 2

Download

Use it from code

What is covered

November 2026

Several days at once

The timetable

Live delays Timetables

Live delays and timetables of FGV: Metrovalencia lines 1 and 2 in Spain, recorded since 7 Oct 2026 from data published on metrovalencia.es and nap.transportes.gob.es, which the archive converts to GTFS-RT and GTFS.

Pick a day on the calendar. Each day is one file with everything recorded that day, in Spain local time. You choose the format on the next page: a spreadsheet (CSV, opens in Excel, LibreOffice or Google Sheets) or Parquet (a compact table format for code).

A file to download
Collected, file ready after 02:15 UTC
Today, still being collected
No data

28 days ready to download. The archive has data for this source since 7 Oct 2026.

Choose the first and last day: you get one zip with a file per day.

The planned timetable: stations, routes, trips and times. It comes as GTFS, the standard timetable format, one Parquet table per GTFS file. 8 versions stored, a new one when FGV: Metrovalencia lines 1 and 2 changes the coming week’s trains.

All versions as Parquet tables

Tools that need a GTFS zip: pip install gtfs-parquet, then gtfs_parquet.write_gtfs(gtfs_parquet.read_parquet(folder), "gtfs.zip") on a folder of the tables. This version was stored on 4 Nov 2026, 15:24 and is the current one.

Accounts are free: you sign in with a code sent to your email, no password.

Every day is a Parquet file at a fixed address. Read it straight from DuckDB, Polars or anything that reads Parquet over HTTP: only the columns and rows your query needs are downloaded. You need a free API token from an account.

Try it in your browser Developer guide

Source id: es-fgv-valencia
Services: TripUpdate live delays: daily files from 7 Oct 2026 to 3 Nov 2026 (28 days)
Daily file: https://data.train-archive.eu/daily/provider=es-fgv-valencia/service=TripUpdate/date=YYYY-MM-DD.parquet final delays per train and stop
Every update: https://data.train-archive.eu/provider=es-fgv-valencia/service=SERVICE/date=YYYY-MM-DD/day.parquet
Today: Still being collected in 15-minute files. The day’s file is built after 02:15 UTC. The developer guide shows how to read the 15-minute files.
Timetables: Service static: 8 versions, listed in es-fgv-valencia/static/latest.json

Live delays on 14 Oct 2026, with DuckDB

INSTALL httpfs; LOAD httpfs;

-- The final delay of each train at each stop, in minutes: the 20 largest
SELECT route, stop_name, scheduled_arrival, arrival_delay_min, delay_source
FROM read_parquet('https://data.train-archive.eu/daily/provider=es-fgv-valencia/service=TripUpdate/date=2026-10-14.parquet?token=YOUR_TOKEN')
WHERE trip_status = 'scheduled'
ORDER BY arrival_delay_min DESC NULLS LAST
LIMIT 20;

The same, in Python with Polars

import polars as pl

token = "YOUR_TOKEN"
day = pl.read_parquet(f"https://data.train-archive.eu/daily/provider=es-fgv-valencia/service=TripUpdate/date=2026-10-14.parquet?token={token}")

# The final delay of each train at each stop, in minutes: the 20 largest
print(
    day.filter(pl.col("trip_status") == "scheduled")
    .select("route", "stop_name", "scheduled_arrival", "arrival_delay_min", "delay_source")
    .sort("arrival_delay_min", descending=True, nulls_last=True)
    .head(20)
)

Or save the file, with curl

curl -L -o es-fgv-valencia-TripUpdate-2026-10-14.parquet \
  'https://data.train-archive.eu/daily/provider=es-fgv-valencia/service=TripUpdate/date=2026-10-14.parquet?token=YOUR_TOKEN'

Replace YOUR_TOKEN with one of your API tokens. Delays are in seconds in the Parquet files; the examples turn them into minutes.

Stations of the current timetable

import json, urllib.request
import polars as pl

base, token = "https://data.train-archive.eu", "YOUR_TOKEN"
latest = json.load(urllib.request.urlopen(f"{base}/es-fgv-valencia/static/latest.json?token={token}"))
stops = pl.read_parquet(f"{base}/{latest['tables']['stops']}?token={token}")
print(stops.select("stop_id", "stop_name"))

Also: every file of this source, listed, and asking an AI assistant to query it for you.

Wednesday 4 November 2026: still being collected

Local time: Europe/Madrid
Rail filter: Off: the feed carries trains only
Live delays: 7 Oct 2026 to 4 Nov 2026, 104 files, 23.2 MB.

3 missing hours

On a usual day the live data covers 91% of the trains the timetable plans. Incomplete days: 7 Oct 2026 (26%, part of the day), 8 Oct 2026 (88%, part of the day), 14 Oct 2026 (91%, part of the day), 15 Oct 2026 (98%, part of the day), 21 Oct 2026 (91%, part of the day).
Feed status: Last update 19:17 on 4 Nov 2026, local time, 227 trains.
Timetables: 8 versions stored.

4 Nov 2026, 15:24 6 files, 78.3 KB current
29 Oct 2026, 15:25 7 files, 86.2 KB
23 Oct 2026, 09:16 7 files, 93.8 KB
20 Oct 2026, 18:22 6 files, 86.3 KB
15 Oct 2026, 18:23 6 files, 87.8 KB
13 Oct 2026, 16:43 7 files, 86.9 KB

60 stops in the latest timetable (every stop: the timetable does not mark stations).

Do you publish this feed? Ask for a change or its removal. Removal stops collection and deletes the files already stored.