ŽSR / ZSSK train delays, Wednesday 11 November 2026

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

From 10 to 19 October 2026 about a quarter of the updates matched no train of the timetable the archive had (30 September; ŽSR's uploads of those days are no longer published), so those days lack the planned stops of many trains: treat them as doubtful. 20 and 21 October were rebuilt against the timetable of 22 October (every update matched).

How late the trains were

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

Trains
1,431
5 min late or more
27% of stops
15 min late or more
7% of stops
Median delay
0 min
Cancelled trains
0

Recorded from 00:00 to 23:04. The figures use the last delay announced at each of the 17,000 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. 100% of the stops of the trains that ran (skipped stops aside) had a delay.

Fewer trains than usual: the archive saw 1,448 of the 2,002 trains the timetable planned (72%, against 100% on a usual day). The feed stopped or repeated old data for part of the day.

No data from 06:00–09:00: the feed was read but sent almost no trains (06:00–09:00), so these figures cover only part of the day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
rj 175 HUNGARIABudapest-Nyugati pu83 min
Ex 631 TATRANTrnava74 min
Os 7935 Kraľovany56 min
R 914 GEMERANZvolen osob.st.56 min
R 961 ZAKARPATIAKošice53 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=sk-zsr/service=TripUpdate/date=2026-11-11.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
Praha hl.n.EC 120 VALAŠSKÝ EXPRES22:510scheduled
Nové ZámkyOs 4818 14:068scheduled
LeviceOs 5227 19:133scheduled
LučenecOs 6219 13:5713scheduled
Brezno mestoOs 7223 16:350scheduled
VrútkyOs 7568 18:451scheduled
KošiceR 913 GEMERAN10:517scheduled
Poprad-TatryOs 8322 16:150scheduled
PrešovOs 9132 21:130scheduled
KútyOs 14291 NAD16:500scheduled
LipanyREX 1948 09:550scheduled
Wien HbfREX 2527 18:5610scheduled
TrenčínOs 3127 18:4025scheduled
ŽilinaOs 3569 15:471scheduled
Dunajská StredaOs 4339 00:080scheduled

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.