Train 3111 Hromec – Zabok
It has not run yet today
Last recorded run: Saturday 17 October No data
Next service: today 03:55 from Hromec · Mon 19 Oct
Next departure 03:55 today · Hromec
On-time · 30 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 no data
On-time · 90 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
Last 30 days
Arrival delay at Zabok, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
| Stop | Sched. |
|---|---|
| 03:55 | |
| 04:02 / 04:03 | |
| 04:06 | |
| 04:08 | |
| 04:11 / 04:12 | |
| 04:15 | |
| 04:18 | |
| 04:21 | |
| 04:24 / 04:25 | |
| 04:28 | |
| 04:33 |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 17 Oct | Zabok 04:34 | No data | — |
| Fri 16 Oct | Zabok 04:34 | No data | — |
| Thu 15 Oct | Zabok 04:34 | No data | — |
| Wed 14 Oct | Zabok 04:34 | No data | — |
| Tue 13 Oct | Zabok 04:34 | No data | — |
| Mon 12 Oct | Zabok 04:34 | No data | — |
| Sat 10 Oct | Zabok 04:34 | No data | — |
| Fri 9 Oct | Zabok 04:34 | No data | — |
| Thu 8 Oct | Zabok 04:34 | No data | — |
| Wed 7 Oct | Zabok 04:34 | No data | — |
| Tue 6 Oct | Zabok 04:34 | No data | — |
| Mon 5 Oct | Zabok 04:34 | No data | — |