Os 15966 15966 Havlíčkův Brod – Humpolec
Alerts for train 15966
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 15966.
It has not run yet today
Last recorded run: Sunday 8 November No data
Next service: today 20:05 from Havlíčkův Brod · Mon 9 Nov
Last 30 days
Arrival delay at Humpolec, 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 +20 min · last fix heading to — +20 min
- Mon 17 Aug Max en route +16 min · last fix heading to — +16 min
- Sun 20 Sept Max en route +17 min · last fix heading to — +15 min
- Fri 11 Sept Max en route +15 min · last fix heading to — +15 min
- Thu 20 Aug Max en route +16 min · last fix heading to — +15 min
Distribution · 90 days
54 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 1
- On time 28% · 15
- 3–10 min 50% · 27
- 10–30 min 20% · 11
- 30+ min 0% · 0
On-time by weekday
- 57% M n=7
- 57% T n=7
- 13% W n=8
- 25% T n=8
- 25% F n=8
- 25% S n=8
- 13% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 54 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 |
|---|---|---|---|
| 20:05 | +6 min | +13 min | |
| 20:10 | ≈ +5 min | ≈ +13 min | |
| 20:13 | ≈ +5 min | ≈ +12 min | |
| 20:17 / 20:18 | ≈ +5 min | ≈ +12 min | |
| 20:22 | ≈ +5 min | ≈ +12 min | |
| 20:28 | ≈ +5 min | ≈ +12 min | |
| 20:30 | ≈ +6 min | ≈ +12 min | |
| 20:33 | ≈ +6 min | ≈ +12 min | |
| 20:38 | ≈ +6 min | ≈ +12 min | |
| 20:46 | +6 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 |
|---|---|---|---|
| Sun 8 Nov | Humpolec 20:47 | No data | — |
| Sat 7 Nov | Humpolec 20:47 | No data | — |
| Fri 6 Nov | Humpolec 20:47 | No data | — |
| Thu 5 Nov | Humpolec 20:47 | No data | — |
| Wed 4 Nov | Humpolec 20:47 | No data | — |
| Tue 3 Nov | Humpolec 20:47 | No data | — |
| Mon 2 Nov | Humpolec 20:47 | No data | — |
| Sun 1 Nov | Humpolec 20:47 | No data | — |
| Sat 31 Oct | Humpolec 20:47 | No data | — |
| Fri 30 Oct | Humpolec 20:47 | No data | — |
| Thu 29 Oct | Humpolec 20:47 | No data | — |
| Wed 28 Oct | Humpolec 20:47 | No data | — |
| Tue 27 Oct | Humpolec 20:48 | No data | — |
| Mon 26 Oct | Humpolec 20:47 | No data | — |
| Sun 25 Oct | Humpolec 20:47 | No data | — |
| Sat 24 Oct | Humpolec 20:47 | No data | — |
| Fri 23 Oct | Humpolec 20:47 | No data | — |
| Thu 22 Oct | Humpolec 20:47 | No data | — |
| Wed 21 Oct | Humpolec 20:47 | No data | — |
| Tue 20 Oct | Humpolec 20:47 | No data | — |
| Mon 19 Oct | Humpolec 20:48 | No data | — |
| Sun 18 Oct | Humpolec 20:47 | No data | — |
| Sat 17 Oct | Humpolec 20:47 | No data | — |
| Fri 16 Oct | Humpolec 20:47 | No data | — |
| Thu 15 Oct | Humpolec 20:47 | No data | — |
| Wed 14 Oct | Humpolec 20:47 | No data | — |
| Tue 13 Oct | Humpolec 20:47 | No data | — |
| Mon 12 Oct | Humpolec 20:48 | No data | — |
| Sun 11 Oct | Humpolec 20:47 | No data | — |
| Sat 10 Oct | Humpolec 20:47 | No data | — |