Os 8959 8959 Kozolupy – Blovice
Alerts for train 8959
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 8959.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 16:10 from Kozolupy · Thu 5 Nov
Last 30 days
Arrival delay at Blovice, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 18 Aug Max en route +15 min · last fix heading to — +12 min
- Thu 3 Sept Max en route +11 min · last fix heading to — +11 min
- Tue 29 Sept Max en route +5 min · last fix heading to — +5 min
- Wed 23 Sept Max en route +5 min · last fix heading to — +5 min
- Wed 16 Sept Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 75% · 30
- 3–10 min 20% · 8
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 63% T n=8
- 50% W n=8
- 75% T n=8
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 40 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 |
|---|---|---|---|
| 16:10 | on time | +1 min | |
| 16:12 | ≈ on time | ≈ +1 min | |
| 16:15 / 16:16 | ≈ on time | ≈ +1 min | |
| 16:18 | ≈ on time | ≈ +2 min | |
| 16:20 / 16:21 | ≈ on time | ≈ +2 min | |
| 16:24 / 16:28 | ≈ +1 min | ≈ +2 min | |
| 16:30 / 16:31 | ≈ +1 min | ≈ +2 min | |
| 16:37 / 16:38 | ≈ +1 min | ≈ +3 min | |
| 16:41 / 16:42 | ≈ +1 min | ≈ +4 min | |
| 16:45 / 16:46 | ≈ +1 min | ≈ +4 min | |
| 16:50 | ≈ +1 min | ≈ +5 min | |
| 16:53 | +1 min | +5 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 4 Nov | Blovice 16:54 | No data | — |
| Tue 3 Nov | Blovice 16:54 | No data | — |
| Mon 2 Nov | Blovice 16:54 | No data | — |
| Fri 30 Oct | Blovice 16:54 | No data | — |
| Thu 29 Oct | Blovice 16:54 | No data | — |
| Tue 27 Oct | Blovice 16:55 | No data | — |
| Mon 26 Oct | Blovice 16:54 | No data | — |
| Fri 23 Oct | Blovice 16:54 | No data | — |
| Thu 22 Oct | Blovice 16:54 | No data | — |
| Wed 21 Oct | Blovice 16:54 | No data | — |
| Tue 20 Oct | Blovice 16:54 | No data | — |
| Mon 19 Oct | Blovice 16:54 | No data | — |
| Fri 16 Oct | Blovice 16:54 | No data | — |
| Thu 15 Oct | Blovice 16:54 | No data | — |
| Wed 14 Oct | Blovice 16:54 | No data | — |
| Tue 13 Oct | Blovice 16:54 | No data | — |
| Mon 12 Oct | Blovice 16:54 | No data | — |
| Fri 9 Oct | Blovice 16:54 | No data | — |
| Thu 8 Oct | Blovice 16:54 | No data | — |
| Wed 7 Oct | Blovice 16:54 | No data | — |
| Tue 6 Oct | Blovice 16:54 | No data | — |
| Mon 5 Oct | Blovice 16:54 | 0 min | — |
| Fri 2 Oct | — 17:06 | −1 min | — |
| Thu 1 Oct | — 17:10 | +3 min | +3 min |
| Wed 30 Sept | — 17:10 | +2 min | +2 min |
| Tue 29 Sept | — 17:12 | +5 min | +5 min |
| Fri 25 Sept | — 17:08 | 0 min | +2 min |
| Thu 24 Sept | — 17:09 | +2 min | +2 min |
| Wed 23 Sept | — 17:13 | +5 min | +5 min |
| Tue 22 Sept | — 17:07 | 0 min | +2 min |