Os 18442 18442 Horní Cerekev – Jihlava
Alerts for train 18442
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 18442.
Running now · updated 07:17
Position estimated from the timetable
Between Jihlava město and Jihlava No data
Estimated arrival at Jihlava 07:20 · 36 km/h
- Horní Cerekev06:40
- Batelov06:47
- Dolní Cerekev06:55
- Dvorce07:04
- Rantířov07:07
- Jihlava město07:16
- Jihlava07:20
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 17 Aug Max en route +5 min · last fix heading to — +5 min
- Wed 26 Aug Max en route +6 min · last fix heading to — +3 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 16
- 3–10 min 11% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 100% T n=2
- 50% W n=2
- 100% T n=2
- 100% F n=2
- 100% S n=7
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 18 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 | Today |
|---|---|---|---|---|
| 06:40 | on time | on time | Passed | |
| 06:43 | ≈ on time | ≈ on time | Passed | |
| 06:47 / 06:48 | ≈ on time | ≈ on time | Passed | |
| 06:55 | ≈ on time | ≈ +1 min | Passed | |
| 06:58 / 06:59 | ≈ on time | ≈ +1 min | Passed | |
| 07:04 | ≈ on time | ≈ +1 min | Passed | |
| 07:07 / 07:08 | ≈ on time | ≈ +2 min | Passed | |
| 07:13 | ≈ on time | ≈ +2 min | Passed | |
| 07:16 / 07:17 | ≈ on time | ≈ +2 min | Passed | |
| 07:20 | on time | +2 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 město 07:14Partial coverage | No data | — |
| Sat 7 Nov | Jihlava 07:19 | No data | — |
| Sat 31 Oct | Jihlava 07:21 | No data | — |
| Wed 28 Oct | Jihlava 07:21 | No data | — |
| Sat 24 Oct | Jihlava 07:21 | No data | — |
| Sat 17 Oct | Jihlava 07:21 | No data | — |
| Sat 10 Oct | Jihlava 07:21 | No data | — |
| Sat 3 Oct | — 07:35 | 0 min | — |
| Sat 26 Sept | — 07:35 | 0 min | — |
| Sat 19 Sept | — 08:17 | 0 min | — |
| Sat 12 Sept | — 07:35 | 0 min | — |
| Sat 5 Sept | — 07:35 | 0 min | +2 min |
| Mon 31 Aug | — 07:35 | 0 min | — |
| Sat 29 Aug | — 07:34 | 0 min | — |
| Fri 28 Aug | — 07:35 | 0 min | — |
| Thu 27 Aug | — 07:36 | 0 min | — |
| Wed 26 Aug | — 07:37 | +3 min | +6 min |
| Tue 25 Aug | — 07:34 | 0 min | — |
| Mon 24 Aug | — 07:34 | 0 min | +1 min |
| Sat 22 Aug | — 07:34 | 0 min | — |
| Fri 21 Aug | — 07:35 | +1 min | +1 min |
| Thu 20 Aug | — 07:35 | 0 min | — |
| Wed 19 Aug | — 07:35 | 0 min | — |
| Tue 18 Aug | — 07:35 | 0 min | — |
| Mon 17 Aug | — 07:40 | +5 min | +5 min |