Os 27342 27342 Stupno – Plzeň hl. n.
Alerts for train 27342
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 27342.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 17:10 from Stupno · Thu 5 Nov
Last 30 days
Arrival delay at Plzeň hl. n., 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 +13 min · last fix heading to — +12 min
- Thu 13 Aug Max en route +10 min · last fix heading to — +10 min
- Fri 11 Sept Max en route +8 min · last fix heading to — +8 min
- Wed 9 Sept Max en route +9 min · last fix heading to — +8 min
- Tue 29 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 56% · 22
- 3–10 min 38% · 15
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 57% M n=7
- 63% T n=8
- 38% 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 (13 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 |
|---|---|---|---|
| 17:10 | on time | on time | |
| 17:12 | ≈ on time | ≈ on time | |
| 17:14 | ≈ on time | ≈ +1 min | |
| 17:17 | ≈ on time | ≈ +1 min | |
| 17:19 | ≈ on time | ≈ +2 min | |
| 17:23 | ≈ on time | ≈ +3 min | |
| 17:25 | ≈ on time | ≈ +3 min | |
| 17:27 / 17:29 | ≈ on time | ≈ +3 min | |
| 17:31 | ≈ +1 min | ≈ +4 min | |
| 17:32 | ≈ +1 min | ≈ +4 min | |
| 17:34 / 17:36 | ≈ +1 min | ≈ +5 min | |
| 17:42 | ≈ +2 min | ≈ +6 min | |
| 17:46 | +2 min | +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 |
|---|---|---|---|
| Wed 4 Nov | Plzeň hl. n. 17:47 | No data | — |
| Tue 3 Nov | Plzeň hl. n. 17:47 | No data | — |
| Mon 2 Nov | Plzeň hl. n. 17:47 | No data | — |
| Fri 30 Oct | Plzeň hl. n. 17:47 | No data | — |
| Thu 29 Oct | Plzeň hl. n. 17:47 | No data | — |
| Tue 27 Oct | Plzeň hl. n. 17:47 | No data | — |
| Mon 26 Oct | Plzeň hl. n. 17:47 | No data | — |
| Fri 23 Oct | Plzeň hl. n. 17:48 | No data | — |
| Thu 22 Oct | Plzeň hl. n. 17:47 | No data | — |
| Wed 21 Oct | Plzeň hl. n. 17:47 | No data | — |
| Tue 20 Oct | Plzeň hl. n. 17:48 | No data | — |
| Mon 19 Oct | Plzeň hl. n. 17:47 | No data | — |
| Fri 16 Oct | Plzeň hl. n. 17:47 | No data | — |
| Thu 15 Oct | Plzeň hl. n. 17:47 | No data | — |
| Wed 14 Oct | Plzeň hl. n. 17:47 | No data | — |
| Tue 13 Oct | Plzeň hl. n. 17:47 | No data | — |
| Mon 12 Oct | Plzeň hl. n. 17:48 | No data | — |
| Fri 9 Oct | Plzeň hl. n. 17:47 | No data | — |
| Thu 8 Oct | Plzeň hl. n. 17:47 | No data | — |
| Wed 7 Oct | Plzeň hl. n. 17:47 | No data | — |
| Tue 6 Oct | Plzeň hl. n. 17:47 | No data | — |
| Mon 5 Oct | Plzeň hl. n. 17:47 | No data | — |
| Fri 2 Oct | — 17:59 | −1 min | — |
| Thu 1 Oct | — 18:01 | +1 min | +1 min |
| Wed 30 Sept | — 18:02 | +1 min | +2 min |
| Tue 29 Sept | — 18:07 | +7 min | +8 min |
| Fri 25 Sept | — 18:02 | 0 min | +1 min |
| Thu 24 Sept | — 18:04 | +4 min | +4 min |
| Wed 23 Sept | — 18:05 | +4 min | +4 min |
| Tue 22 Sept | — 18:01 | 0 min | +4 min |