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