Os 8962 8962 Plzeň hl. n. – Kozolupy
Alerts for train 8962
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 8962.
✓ Today’s run finished
Today, last fix heading to Kozolupy at 20:28 No data
- Plzeň hl. n.20:14
- Plzeň-Jižní Předměstí20:16
- Plzeň-Zadní Skvrňany20:19
- Plzeň-Křimice20:21
- Vochov20:24
- Kozolupy20:27
Next service: Monday 20:14 from Plzeň hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Kozolupy, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 19 Aug Max en route +13 min · last fix heading to — +13 min
- Fri 21 Aug Max en route +12 min · last fix heading to — +12 min
- Tue 18 Aug Max en route +12 min · last fix heading to — +12 min
- Wed 9 Sept Max en route +8 min · last fix heading to — +8 min
- Fri 11 Sept Max en route +8 min · last fix heading to — +7 min
Distribution · 90 days
39 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 69% · 27
- 3–10 min 23% · 9
- 10–30 min 8% · 3
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 63% T n=8
- 63% W n=8
- 75% T n=8
- 75% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 39 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:14 | on time | +6 min | |
| 20:16 / 20:17 | ≈ on time | ≈ +7 min | |
| 20:19 | ≈ on time | ≈ +7 min | |
| 20:21 / 20:22 | ≈ on time | ≈ +7 min | |
| 20:24 | ≈ on time | ≈ +7 min | |
| 20:27 | on time | +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 | Kozolupy 20:28 | No data | — |
| Thu 5 Nov | Kozolupy 20:28 | No data | — |
| Wed 4 Nov | Kozolupy 20:28 | No data | — |
| Tue 3 Nov | Kozolupy 20:28 | No data | — |
| Mon 2 Nov | Kozolupy 20:28 | No data | — |
| Fri 30 Oct | Kozolupy 20:28 | No data | — |
| Thu 29 Oct | Kozolupy 20:28 | No data | — |
| Tue 27 Oct | Kozolupy 20:29 | No data | — |
| Mon 26 Oct | Kozolupy 20:28 | No data | — |
| Fri 23 Oct | Kozolupy 20:28 | No data | — |
| Thu 22 Oct | Kozolupy 20:28 | No data | — |
| Wed 21 Oct | Kozolupy 20:28 | No data | — |
| Tue 20 Oct | Kozolupy 20:28 | No data | — |
| Mon 19 Oct | Kozolupy 20:28 | No data | — |
| Fri 16 Oct | Kozolupy 20:28 | No data | — |
| Thu 15 Oct | Kozolupy 20:28 | No data | — |
| Wed 14 Oct | Kozolupy 20:28 | No data | — |
| Tue 13 Oct | Kozolupy 20:28 | No data | — |
| Mon 12 Oct | Kozolupy 20:29 | No data | — |
| Fri 9 Oct | Kozolupy 20:28 | No data | — |
| Thu 8 Oct | Kozolupy 20:28 | No data | — |
| Wed 7 Oct | Kozolupy 20:28 | No data | — |
| Tue 6 Oct | Kozolupy 20:28 | No data | — |
| Mon 5 Oct | Kozolupy 20:28 | No data | — |
| Fri 2 Oct | — 20:42 | 0 min | — |
| Thu 1 Oct | — 20:42 | 0 min | +1 min |
| Wed 30 Sept | — 20:41 | 0 min | — |
| Tue 29 Sept | — 20:45 | +3 min | +3 min |
| Fri 25 Sept | — 20:43 | 0 min | +1 min |
| Thu 24 Sept | — 20:42 | 0 min | — |