Os 7452 7452 Plzeň hl. n. – Stod
Alerts for train 7452
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 7452.
✓ Today’s run finished
Today, last fix heading to Stod at 11:49 No data
- Plzeň hl. n.11:20
- Plzeň-Jižní Předměstí11:22
- Vejprnice11:29
- Tlučná11:33
- Nýřany11:36
- Chotěšov u Stoda11:45
- Stod11:50
Next service: Monday 11:20 from Plzeň hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Stod, 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 +11 min · last fix heading to — +11 min
- Thu 3 Sept Max en route +12 min · last fix heading to — +10 min
- Thu 1 Oct Max en route +5 min · last fix heading to — +4 min
- Tue 15 Sept Max en route +5 min · last fix heading to — +4 min
- Tue 1 Sept Max en route +4 min · last fix heading to — +4 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 60% · 24
- 3–10 min 35% · 14
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 50% M n=8
- 63% T n=8
- 63% W n=8
- 63% T n=8
- 63% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 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 |
|---|---|---|---|
| 11:20 | on time | +3 min | |
| 11:22 | ≈ on time | ≈ +3 min | |
| 11:24 / 11:25 | ≈ on time | ≈ +3 min | |
| 11:29 / 11:30 | ≈ on time | ≈ +3 min | |
| 11:33 | ≈ +1 min | ≈ +3 min | |
| 11:36 / 11:38 | ≈ +1 min | ≈ +3 min | |
| 11:42 | ≈ +1 min | ≈ +3 min | |
| 11:45 / 11:46 | ≈ +1 min | ≈ +3 min | |
| 11:50 | +1 min | +4 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 | Stod 11:49 | No data | — |
| Thu 5 Nov | Stod 11:49 | No data | — |
| Wed 4 Nov | Stod 11:49 | No data | — |
| Tue 3 Nov | Stod 11:49 | No data | — |
| Mon 2 Nov | Stod 11:49 | No data | — |
| Fri 30 Oct | Stod 11:51 | No data | — |
| Thu 29 Oct | Stod 11:51 | No data | — |
| Tue 27 Oct | Stod 11:51 | No data | — |
| Mon 26 Oct | Stod 11:51 | No data | — |
| Fri 23 Oct | Stod 11:51 | No data | — |
| Thu 22 Oct | Stod 11:51 | No data | — |
| Wed 21 Oct | Stod 11:51 | No data | — |
| Tue 20 Oct | Stod 11:51 | No data | — |
| Mon 19 Oct | Stod 11:51 | No data | — |
| Fri 16 Oct | Stod 11:51 | No data | — |
| Thu 15 Oct | Stod 11:51 | No data | — |
| Wed 14 Oct | Stod 11:51 | No data | — |
| Tue 13 Oct | Stod 11:51 | No data | — |
| Mon 12 Oct | Stod 11:51 | No data | — |
| Fri 9 Oct | Stod 11:51 | No data | — |
| Thu 8 Oct | Stod 11:51 | No data | — |
| Wed 7 Oct | Stod 11:51 | No data | — |
| Tue 6 Oct | Stod 11:51 | No data | — |
| Mon 5 Oct | — 12:07 | +3 min | +4 min |
| Fri 2 Oct | — 12:08 | +3 min | +5 min |
| Thu 1 Oct | — 12:09 | +4 min | +5 min |
| Wed 30 Sept | — 12:07 | +3 min | +4 min |
| Tue 29 Sept | — 12:06 | +2 min | +4 min |
| Fri 25 Sept | — 12:05 | +1 min | +2 min |
| Thu 24 Sept | — 12:06 | +1 min | +3 min |