Os 5332 5332 Chrudim – Pardubice hl. n.
Alerts for train 5332
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 5332.
It has not run yet today
Last recorded run: Sunday 8 November No data
Next service: today 07:14 from Chrudim · Mon 9 Nov
Last 30 days
Arrival delay at Pardubice 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
- Thu 10 Sept Max en route +16 min · last fix heading to — +14 min
- Tue 29 Sept Max en route +11 min · last fix heading to — +8 min
- Thu 17 Sept Max en route +10 min · last fix heading to — +8 min
- Mon 21 Sept Max en route +9 min · last fix heading to — +7 min
- Fri 11 Sept Max en route +6 min · last fix heading to — +5 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 11% · 6
- On time 67% · 37
- 3–10 min 20% · 11
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 86% T n=7
- 75% W n=8
- 50% T n=8
- 63% F n=8
- 100% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 55 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 |
|---|---|---|---|
| 07:14 | on time | +1 min | |
| 07:16 | ≈ on time | ≈ +1 min | |
| 07:18 / 07:19 | ≈ on time | ≈ +2 min | |
| 07:22 | ≈ on time | ≈ +2 min | |
| 07:25 | ≈ on time | ≈ +3 min | |
| 07:29 / 07:32 | ≈ on time | ≈ +4 min | |
| 07:35 | on time | +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 |
|---|---|---|---|
| Sun 8 Nov | Pardubice hl. n. 07:34 | No data | — |
| Sat 7 Nov | Pardubice hl. n. 07:34 | No data | — |
| Fri 6 Nov | Pardubice centrum 07:39 | No data | — |
| Thu 5 Nov | Pardubice centrum 07:39 | No data | — |
| Wed 4 Nov | Pardubice centrum 07:39 | No data | — |
| Tue 3 Nov | Pardubice centrum 07:39 | No data | — |
| Mon 2 Nov | Pardubice centrum 07:39 | No data | — |
| Sun 1 Nov | Pardubice hl. n. 07:36 | No data | — |
| Sat 31 Oct | Pardubice hl. n. 07:36 | No data | — |
| Fri 30 Oct | Pardubice centrum 07:40 | No data | — |
| Thu 29 Oct | Pardubice centrum 07:40 | No data | — |
| Wed 28 Oct | Pardubice hl. n. 07:36 | No data | — |
| Tue 27 Oct | Pardubice centrum 07:40 | No data | — |
| Mon 26 Oct | Pardubice centrum 07:40 | No data | — |
| Sun 25 Oct | Pardubice hl. n. 07:36 | No data | — |
| Sat 24 Oct | Pardubice hl. n. 07:36 | No data | — |
| Fri 23 Oct | Pardubice centrum 07:40 | No data | — |
| Thu 22 Oct | Pardubice centrum 07:40 | No data | — |
| Wed 21 Oct | Pardubice centrum 07:40 | No data | — |
| Tue 20 Oct | Pardubice centrum 07:40 | No data | — |
| Mon 19 Oct | Pardubice centrum 07:40 | No data | — |
| Sun 18 Oct | Pardubice hl. n. 07:36 | No data | — |
| Sat 17 Oct | Pardubice hl. n. 07:36 | No data | — |
| Fri 16 Oct | Pardubice centrum 07:40 | No data | — |
| Thu 15 Oct | Pardubice centrum 07:40 | No data | — |
| Wed 14 Oct | Pardubice centrum 07:40 | No data | — |
| Tue 13 Oct | Pardubice centrum 07:40 | No data | — |
| Mon 12 Oct | Pardubice centrum 07:40 | No data | — |
| Sun 11 Oct | Pardubice hl. n. 07:36 | No data | — |
| Sat 10 Oct | Pardubice hl. n. 07:36 | No data | — |