Os 14816 14816 Třebíč – Jihlava
Alerts for train 14816
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 14816.
It has not run yet today
Last recorded run: Saturday 14 November No data
Next service: today 13:15 from Třebíč · Sun 15 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
- Sun 30 Aug Max en route +10 min · last fix heading to — +7 min
- Sat 22 Aug Max en route +11 min · last fix heading to — +6 min
- Sat 19 Sept Max en route +7 min · last fix heading to — +5 min
- Sat 26 Sept Max en route +8 min · last fix heading to — +4 min
- Sun 13 Sept Max en route +5 min · last fix heading to — +4 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 60% · 9
- 3–10 min 40% · 6
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 57% S n=7
- 57% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 15 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 |
|---|---|---|---|
| 13:15 | +3 min | +7 min | |
| 13:18 | ≈ +3 min | ≈ +7 min | |
| 13:23 | ≈ +3 min | ≈ +7 min | |
| 13:30 | ≈ +3 min | ≈ +7 min | |
| 13:35 / 13:36 | ≈ +3 min | ≈ +7 min | |
| 13:39 | ≈ +3 min | ≈ +7 min | |
| 13:42 | ≈ +2 min | ≈ +6 min | |
| 13:45 | ≈ +2 min | ≈ +6 min | |
| 13:48 / 13:49 | ≈ +2 min | ≈ +6 min | |
| 13:52 / 13:56 | ≈ +2 min | ≈ +6 min | |
| 14:03 / 14:04 | ≈ +2 min | ≈ +6 min | |
| 14:08 | +2 min | +6 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 |
|---|---|---|---|
| Sat 14 Nov | Jihlava 14:09 | No data | — |
| Sun 8 Nov | Jihlava 14:09 | No data | — |
| Sat 7 Nov | Jihlava 14:09 | No data | — |
| Sun 1 Nov | Jihlava 14:09 | No data | — |
| Sat 31 Oct | Jihlava 14:09 | No data | — |
| Wed 28 Oct | Jihlava 14:09 | No data | — |
| Sun 25 Oct | Jihlava 14:09 | No data | — |
| Sat 24 Oct | Jihlava 14:09 | No data | — |
| Sun 18 Oct | Jihlava 14:09 | No data | — |
| Sat 17 Oct | Jihlava 14:09 | No data | — |
| Sun 11 Oct | Jihlava 14:09 | No data | — |
| Sat 10 Oct | Jihlava 14:09 | No data | — |
| Sun 4 Oct | — 14:16 | 0 min | — |
| Sat 3 Oct | — 14:16 | 0 min | — |
| Mon 28 Sept | — 14:23 | +1 min | +3 min |
| Sun 27 Sept | — 14:24 | +2 min | +6 min |
| Sat 26 Sept | — 14:27 | +4 min | +8 min |
| Sun 20 Sept | — 14:25 | +2 min | +7 min |
| Sat 19 Sept | — 14:28 | +5 min | +7 min |
| Sun 13 Sept | — 14:26 | +4 min | +5 min |
| Sat 12 Sept | — 14:23 | 0 min | +3 min |
| Sun 6 Sept | — 14:23 | 0 min | +2 min |
| Sat 5 Sept | — 14:25 | +2 min | +5 min |
| Sun 30 Aug | — 14:29 | +7 min | +10 min |
| Sat 29 Aug | — 14:23 | 0 min | +2 min |
| Sun 23 Aug | — 14:25 | +3 min | +6 min |
| Sat 22 Aug | — 14:28 | +6 min | +11 min |