Os 14824 14824 Třebíč – Jihlava
Alerts for train 14824
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 14824.
It does not run today
Last recorded run: Friday 13 November No data
Next service: tomorrow 16:17 from Třebíč · Mon 16 Nov
Last 30 days
Arrival delay at Jihlava, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 21 Aug Max en route +23 min · last fix heading to — +22 min
- Thu 20 Aug Max en route +18 min · last fix heading to — +18 min
- Tue 22 Sept Max en route +14 min · last fix heading to — +13 min
- Mon 7 Sept Max en route +15 min · last fix heading to — +13 min
- Wed 19 Aug Max en route +13 min · last fix heading to — +13 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 29% · 10
- 3–10 min 47% · 16
- 10–30 min 24% · 8
- 30+ min 0% · 0
On-time by weekday
- 33% M n=6
- 43% T n=7
- 43% W n=7
- 29% T n=7
- 0% F n=7
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 34 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 16:17 | on time | on time | |
| 16:20 | ≈ on time | ≈ +1 min | |
| 16:25 | ≈ +1 min | ≈ +2 min | |
| 16:32 | ≈ +2 min | ≈ +4 min | |
| 16:38 | ≈ +3 min | ≈ +5 min | |
| 16:42 / 16:45 | ≈ +3 min | ≈ +6 min | |
| 16:48 / 16:49 | ≈ +4 min | ≈ +7 min | |
| 16:52 | ≈ +4 min | ≈ +8 min | |
| 16:55 / 16:56 | ≈ +5 min | ≈ +9 min | |
| 16:58 / 16:59 | ≈ +5 min | ≈ +10 min | |
| 17:06 / 17:07 | ≈ +6 min | ≈ +12 min | |
| 17:11 | +7 min | +13 min |
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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 13 Nov | Jihlava 17:12 | No data | — |
| Thu 12 Nov | Jihlava 17:12 | No data | — |
| Wed 11 Nov | Jihlava 17:12 | No data | — |
| Tue 10 Nov | Jihlava 17:12 | No data | — |
| Mon 9 Nov | Jihlava 17:12 | No data | — |
| Fri 6 Nov | Jihlava 17:12 | No data | — |
| Thu 5 Nov | Jihlava 17:12 | No data | — |
| Wed 4 Nov | Jihlava 17:12 | No data | — |
| Tue 3 Nov | Jihlava 17:12 | No data | — |
| Mon 2 Nov | Jihlava 17:12 | No data | — |
| Fri 30 Oct | Jihlava 17:12 | No data | — |
| Thu 29 Oct | Jihlava 17:12 | No data | — |
| Tue 27 Oct | Jihlava 17:13 | No data | — |
| Mon 26 Oct | Jihlava 17:12 | No data | — |
| Fri 23 Oct | Jihlava 17:12 | No data | — |
| Thu 22 Oct | Jihlava 17:12 | No data | — |
| Wed 21 Oct | Jihlava 17:12 | No data | — |
| Tue 20 Oct | Jihlava 17:13 | No data | — |
| Mon 19 Oct | Jihlava 17:12 | No data | — |
| Fri 16 Oct | Jihlava 17:12 | No data | — |
| Thu 15 Oct | Jihlava 17:12 | No data | — |
| Wed 14 Oct | Jihlava 17:12 | No data | — |
| Tue 13 Oct | Jihlava 17:12 | No data | — |
| Mon 12 Oct | Jihlava 17:12 | No data | — |
| Fri 9 Oct | Jihlava 17:12 | No data | — |
| Thu 8 Oct | Jihlava 17:12 | No data | — |
| Wed 7 Oct | Jihlava 17:12 | No data | — |
| Tue 6 Oct | Jihlava 17:12 | No data | — |
| Mon 5 Oct | Jihlava 17:12 | +2 min | +2 min |
| Fri 2 Oct | — 17:20 | +4 min | +4 min |