ŽSR / ZSSK train delays, Saturday 24 October 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
80% of stops were reached less than 5 minutes late, and half of them within 0 minutes of the timetable.
- Trains
- 931
- 5 min late or more
- 20% of stops
- 15 min late or more
- 5% of stops
- Median delay
- 0 min
- Cancelled trains
- 0
Recorded from 00:00 to 23:59. The figures use the last delay announced at each of the 11,718 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 931 of the 1,559 trains the timetable planned (60%, against 100% on a usual day). The feed stopped or repeated old data for part of the day.
Not counted in the trains planned: 1 more train the timetable lists on lines the live feed has not carried in the week before (Železničná spoločnosť Slovensko, a.s.).
No data from 06:00–12:00: the feed could not be read (06:00–12:00), so these figures cover only part of the day.
Most delayed trains
| Line | Left its first stop | Where it was latest | Delay |
|---|---|---|---|
| rj 175 HUNGARIA | Budapest-Nyugati pu | 119 min | |
| Os 7856 | Liptovský Mikuláš | 61 min | |
| REX 1764 | Poprad-Tatry | 60 min | |
| REX 1783 | Helcmanovce | 59 min | |
| REX 1784 | Margecany | 50 min |
Download
Get the CSV Accounts are free: you sign in with a code sent to your email, no password. You come back here after signing in.
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-10-24.parquet?token=YOUR_TOKEN
A few rows of the file
15 different trains, each at one stop. The CSV has more columns, listed below.
Stop stop_name | Line route | Arrival predicted_arrival | Delay (min) arrival_delay_min | Status trip_status |
|---|---|---|---|---|
| Praha hl.n. | EC 120 VALAŠSKÝ EXPRES | 22:51 | 0 | scheduled |
| Komárno | Os 4819 | 13:36 | 9 | scheduled |
| Nové Zámky | Os 5214 | 13:06 | 0 | scheduled |
| Bratislava-N.Mesto | R 746 PONITRAN | 13:03 | 3 | scheduled |
| Brezno | Os 6784 | 18:27 | 0 | scheduled |
| Martin | Os 7555 | 19:21 | 0 | scheduled |
| Kraľovany | Os 7930 | 20:46 | 0 | scheduled |
| Tatranská Lomnica | Os 8228 | 18:20 | 0 | scheduled |
| Banská Bystrica | R 943 FATRAN | 19:27 | 2 | scheduled |
| Bratislava hl.st. | R 10726 POVAŽAN | 18:15 | 0 | scheduled |
| Trnava | REX 1808 | 12:51 | 0 | scheduled |
| Bratislava hl.st. | Os 2031 | 19:45 | 0 | scheduled |
| Myjava | Os 2719 | 17:51 | 0 | scheduled |
| Žilina | Os 3333 | 21:11 | -1 | scheduled |
| Bratislava hl.st. | Os 4332 | 21:25 | 0 | scheduled |
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.