Os 14812 14812 Třebíč – Jihlava
Alerts for train 14812
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 14812.
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 10:17 from Třebíč · Mon 9 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
- Mon 31 Aug Max en route +15 min · last fix heading to — +13 min
- Thu 17 Sept Max en route +10 min · last fix heading to — +9 min
- Fri 18 Sept Max en route +9 min · last fix heading to — +7 min
- Tue 8 Sept Max en route +12 min · last fix heading to — +7 min
- Fri 4 Sept Max en route +9 min · last fix heading to — +7 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 50% · 17
- 3–10 min 47% · 16
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 71% T n=7
- 29% W n=7
- 43% T n=7
- 29% 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 |
|---|---|---|---|
| 10:17 | +1 min | +4 min | |
| 10:20 | ≈ +1 min | ≈ +4 min | |
| 10:25 | ≈ +2 min | ≈ +4 min | |
| 10:32 | ≈ +2 min | ≈ +4 min | |
| 10:38 | ≈ +2 min | ≈ +4 min | |
| 10:42 / 10:46 | ≈ +2 min | ≈ +5 min | |
| 10:49 | ≈ +2 min | ≈ +5 min | |
| 10:52 / 10:53 | ≈ +2 min | ≈ +5 min | |
| 10:56 | ≈ +2 min | ≈ +5 min | |
| 10:59 / 11:00 | ≈ +2 min | ≈ +6 min | |
| 11:07 / 11:08 | ≈ +2 min | ≈ +6 min | |
| 11:12 | +3 min | +7 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 6 Nov | Jihlava 11:13 | No data | — |
| Thu 5 Nov | Jihlava 11:13 | No data | — |
| Wed 4 Nov | Jihlava 11:13 | No data | — |
| Tue 3 Nov | Jihlava 11:13 | No data | — |
| Mon 2 Nov | Jihlava 11:13 | No data | — |
| Fri 30 Oct | Jihlava 11:13 | No data | — |
| Thu 29 Oct | Jihlava 11:13 | No data | — |
| Tue 27 Oct | Jihlava 11:13 | No data | — |
| Mon 26 Oct | Jihlava 11:13 | No data | — |
| Fri 23 Oct | Jihlava 11:13 | No data | — |
| Thu 22 Oct | Jihlava 11:13 | No data | — |
| Wed 21 Oct | Jihlava 11:13 | No data | — |
| Tue 20 Oct | Jihlava 11:13 | No data | — |
| Mon 19 Oct | Jihlava 11:13 | No data | — |
| Fri 16 Oct | Jihlava 11:13 | No data | — |
| Thu 15 Oct | Jihlava 11:13 | No data | — |
| Wed 14 Oct | Jihlava 11:13 | No data | — |
| Tue 13 Oct | Jihlava 11:13 | No data | — |
| Mon 12 Oct | Jihlava 11:13 | No data | — |
| Fri 9 Oct | Jihlava 11:13 | No data | — |
| Thu 8 Oct | Jihlava 11:13 | No data | — |
| Wed 7 Oct | Jihlava 11:13 | No data | — |
| Tue 6 Oct | Jihlava 11:13 | No data | — |
| Fri 25 Sept | — 11:27 | 0 min | +7 min |
| Thu 24 Sept | — 11:27 | 0 min | +6 min |
| Wed 23 Sept | — 11:32 | +5 min | +8 min |
| Tue 22 Sept | — 11:28 | +2 min | +5 min |
| Mon 21 Sept | — 11:29 | +2 min | +4 min |
| Fri 18 Sept | — 11:33 | +7 min | +9 min |
| Thu 17 Sept | — 11:36 | +9 min | +10 min |