Elron

Live delays Train positions Timetables Unofficial source

Live delays, train positions and timetables of Elron in Estonia, recorded since 28 Sep 2026 from GTFS-RT and GTFS feeds.

Download

Pick a day on the calendar. Each day is one file with everything recorded that day, in Estonia 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).

‹ October 2026

November 2026

Train positions of Elron in November 2026. Days with a file are links.
MonTueWedThuFriSatSun
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 Saturday 21 November 2026: still being collected 22
23 24 25 26 27 28 29
30
  • A file to download
  • Collected, file ready after 02:15 UTC
  • Today, still being collected
  • No data

54 days ready to download. The archive has data for this source since 28 Sep 2026.

Several days at once

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

File type

The timetable

The planned timetable: stations, routes, trips and times. It comes as GTFS, the standard timetable format, one Parquet table per GTFS file. 5 versions stored, a new one when Elron 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 17 Nov 2026, 02:04 and is the current one.

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

Use it from code

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
ee-elron
Services
TripUpdate live delays: daily files from 28 Sep 2026 to 20 Nov 2026 (54 days)
VehiclePosition train positions: daily files from 28 Sep 2026 to 20 Nov 2026 (54 days)
Daily file
https://data.train-archive.eu/daily/provider=ee-elron/service=TripUpdate/date=YYYY-MM-DD.parquet final delays per train and stop
Every update
https://data.train-archive.eu/provider=ee-elron/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: 5 versions, listed in ee-elron/static/latest.json
Train positions on 16 Nov 2026, with DuckDB
INSTALL httpfs; LOAD httpfs;

-- The most recent positions of the day
SELECT trip_tripId, vehicle_label, position_latitude, position_longitude, lastSeen
FROM read_parquet('https://data.train-archive.eu/provider=ee-elron/service=VehiclePosition/date=2026-11-16/day.parquet?token=YOUR_TOKEN')
WHERE position_latitude IS NOT NULL
ORDER BY lastSeen DESC
LIMIT 20;
The same, in Python with Polars
import polars as pl

token = "YOUR_TOKEN"
df = pl.read_parquet(f"https://data.train-archive.eu/provider=ee-elron/service=VehiclePosition/date=2026-11-16/day.parquet?token={token}")

# The most recent positions of the day
print(
    df.filter(pl.col("position_latitude").is_not_null())
    .select("trip_tripId", "vehicle_label", "position_latitude", "position_longitude", "lastSeen")
    .sort("lastSeen", descending=True)
    .head(20)
)
Or save the file, with curl
curl -L -o ee-elron-VehiclePosition-2026-11-16.parquet \
  'https://data.train-archive.eu/provider=ee-elron/service=VehiclePosition/date=2026-11-16/day.parquet?token=YOUR_TOKEN'

Replace YOUR_TOKEN with one of your API tokens. Times are in UTC.

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}/ee-elron/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.

What is covered

Local time
Europe/Tallinn
Rail filter
Off: the feed carries trains only
Relayed by
Transitous, jbb.ghsq.de
Live delays
28 Sep 2026 to 21 Nov 2026, 89 files, 16.5 MB.
15 missing hours

    Archive outage on 29 Sep 2026, 06:00 to 13:15: the archive recorded nothing from any source (the archive's collector ran out of memory and restarted in a loop). Our fault, not the source’s.

    On a usual day the live data covers 100% of the trains the timetable plans. Incomplete days: 28 Sep 2026 (19%, part of the day), 29 Sep 2026 (85%, part of the day), 24 Oct 2026 (54%, part of the day).

    Train positions
    28 Sep 2026 to 21 Nov 2026, 89 files, 60.8 MB. No missing hours.

    Archive outage on 29 Sep 2026, 06:00 to 13:15: the archive recorded nothing from any source (the archive's collector ran out of memory and restarted in a loop). Our fault, not the source’s.

    Feed status, live delays
    Last update 09:00 on 21 Nov 2026, local time, 21 trains. Last error: HTTPSConnectionPool(host='crowdsourcing.transitous.org', port=443): Max retries exceeded with url: /gtfsrt/ee-elron/trip-updates.pb (Caused by NewConnectionError("HTTPSConnection(host='crowdsourcing.t
    Feed status, train positions
    Last update 09:00 on 21 Nov 2026, local time, 21 trains. Last error: HTTPSConnectionPool(host='jbb.ghsq.de', port=443): Max retries exceeded with url: /gtfs/elron/VehiclePositions (Caused by NewConnectionError("HTTPSConnection(host='jbb.ghsq.de', port=443): Failed to e
    Timetables
    5 versions stored.
    • 17 Nov 2026, 02:04 8 files, 275.4 KB current
    • 4 Nov 2026, 02:04 6 files, 168.2 KB
    • 2 Nov 2026, 02:04 7 files, 306.0 KB
    • 22 Oct 2026, 13:02 5 files, 132.3 KB
    • 28 Sep 2026, 19:44 11 files, 832.0 KB

    Unofficial source: the operator does not publish this data as GTFS, and volunteers convert or relay it. It can stop at any time.

    18,054 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.