HŽ Putnički prijevoz train delays, Sunday 4 October 2026

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

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
188
5 min late or more
27% of stops
15 min late or more
10% of stops
Median delay
0 min
Cancelled trains
0

Recorded from 00:00 to 15:59. The figures use the last delay announced at each of the 2,822 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 2 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.

Fewer trains than usual: the archive saw 173 of the 323 trains the timetable planned (54%, against 94% 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 (HŽ Putnicki prijevoz).

No data from 16:00–22:00: the feed repeated the same data (18:00–22:00), so these figures cover only part of the day.

Most delayed trains

LineLeft its first stopWhere it was latestDelay
Split - OsijekZdenci-Orahovica65 min
Kotoriba - Zaboki-o77350 min
Ivanić Grad - Savski MarofPrečec stajalište49 min
Zagreb Glavni kolodvor - ČakovecČakovec45 min
Rijeka - Zagreb Glavni kolodvorZlobin30 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=hr-hzpp/service=TripUpdate/date=2026-10-04.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
Zagreb Glavni kolodvorRijeka - Zagreb Glavni kolodvor09:599scheduled
HarmicaNovoselec - Harmica06:510scheduled
HarmicaNovoselec - Harmica13:310scheduled
BjelovarZagreb Glavni kolodvor - Bjelovar10:300scheduled
VinkovciZaprešić - Vinkovci12:5816scheduled
Zagreb Glavni kolodvorOsijek - Zagreb Glavni kolodvor12:570scheduled
GunjaVinkovci - Gunja15:580scheduled
ZabokZagreb Glavni kolodvor - Zabok15:150scheduled
ZabokGornja Stubica - Zabok12:220scheduled
PločeMetković - Ploče10:415scheduled
BuzetPula - Buzet10:440scheduled
Zagreb Glavni kolodvor - Volinja0scheduled
Knin - Šibenik0scheduled
OsijekBeli Manastir - Osijek11:190scheduled
VelikaNova Kapela-Batrina - Velika15:420scheduled

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.