Os 15950 15950 Havlíčkův Brod – Humpolec
Alerts for train 15950
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 15950.
✓ Today’s run finished
Today, last fix heading to Humpolec at 05:04 No data
- Havlíčkův Brod04:24
- Petrkov04:32
- Lípa04:36
- Herálec04:47
- Slavníč04:49
- Plačkov04:57
- Humpolec05:05
Next service: tomorrow 04:24 from Havlíčkův Brod · Thu 12 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 2 Oct Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 6% · 2
- On time 92% · 33
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 100% T n=7
- 100% W n=7
- 100% T n=7
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 04:24 | on time | on time | |
| 04:29 | ≈ on time | ≈ on time | |
| 04:32 | ≈ on time | ≈ on time | |
| 04:36 / 04:37 | ≈ on time | ≈ +1 min | |
| 04:41 | ≈ on time | ≈ +1 min | |
| 04:47 | ≈ on time | ≈ +1 min | |
| 04:49 | ≈ on time | ≈ +1 min | |
| 04:52 | ≈ on time | ≈ +1 min | |
| 04:57 | ≈ on time | ≈ +2 min | |
| 05:05 | 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 |
|---|---|---|---|
| Wed 11 Nov | Humpolec 05:04 | No data | — |
| Tue 10 Nov | Humpolec 05:04 | No data | — |
| Mon 9 Nov | Humpolec 05:04 | No data | — |
| Fri 6 Nov | Humpolec 05:04 | No data | — |
| Thu 5 Nov | Humpolec 05:04 | No data | — |
| Wed 4 Nov | Humpolec 05:04 | No data | — |
| Tue 3 Nov | Humpolec 05:05 | No data | — |
| Mon 2 Nov | Humpolec 05:04 | No data | — |
| Fri 30 Oct | Humpolec 05:06 | No data | — |
| Thu 29 Oct | Humpolec 05:06 | No data | — |
| Tue 27 Oct | Humpolec 05:06 | No data | — |
| Mon 26 Oct | Humpolec 05:06 | No data | — |
| Fri 23 Oct | Humpolec 05:06 | No data | — |
| Thu 22 Oct | Humpolec 05:06 | No data | — |
| Wed 21 Oct | Humpolec 05:06 | No data | — |
| Tue 20 Oct | Humpolec 05:06 | No data | — |
| Mon 19 Oct | Humpolec 05:06 | No data | — |
| Fri 16 Oct | Humpolec 05:06 | No data | — |
| Thu 15 Oct | Humpolec 05:06 | No data | — |
| Wed 14 Oct | Humpolec 05:06 | No data | — |
| Tue 13 Oct | Humpolec 05:06 | No data | — |
| Mon 12 Oct | Humpolec 05:06 | No data | — |
| Fri 9 Oct | Humpolec 05:06 | No data | — |
| Thu 8 Oct | Humpolec 05:06 | No data | — |
| Wed 7 Oct | Humpolec 05:06 | No data | — |
| Tue 6 Oct | Humpolec 05:06 | No data | — |
| Mon 5 Oct | — 05:19 | −1 min | — |
| Fri 2 Oct | — 05:22 | +3 min | +3 min |
| Thu 1 Oct | — 05:20 | +1 min | +1 min |
| Wed 30 Sept | — 05:19 | 0 min | — |