Os 5351 5351 Pardubice hl. n. – Chrudim
Alerts for train 5351
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 5351.
✓ Today’s run finished
Today, last fix heading to Chrudim at 01:29 No data
- Pardubice hl. n.01:08
- Pardubice-Rosice n.L.01:11
- Pardubice závodiště01:15
- Staré Jesenčany01:18
- Medlešice01:22
- Chrudim zastávka01:25
- Chrudim01:28
Next service: tomorrow 01:08 from Pardubice hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Chrudim, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 7 Sept Max en route +16 min · last fix heading to — +14 min
- Sat 29 Aug Max en route +18 min · last fix heading to — +14 min
- Wed 19 Aug Max en route +23 min · last fix heading to — +14 min
- Sat 22 Aug Max en route +27 min · last fix heading to — +13 min
- Mon 17 Aug Max en route +42 min · last fix heading to — +13 min
Distribution · 90 days
49 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 4% · 2
- On time 53% · 26
- 3–10 min 20% · 10
- 10–30 min 22% · 11
- 30+ min 0% · 0
On-time by weekday
- 50% M n=8
- 67% T n=6
- 57% W n=7
- 43% T n=7
- 88% F n=8
- 29% S n=7
- 67% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 49 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 |
|---|---|---|---|
| 01:08 | +3 min | +21 min | |
| 01:11 / 01:13 | ≈ +3 min | ≈ +19 min | |
| 01:15 | ≈ +3 min | ≈ +17 min | |
| 01:18 | ≈ +3 min | ≈ +16 min | |
| 01:22 | ≈ +2 min | ≈ +15 min | |
| 01:25 | ≈ +2 min | ≈ +13 min | |
| 01:28 | +2 min | +13 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 | Chrudim 01:29 | No data | — |
| Sat 7 Nov | Chrudim 01:29 | No data | — |
| Fri 6 Nov | Chrudim 01:29 | No data | — |
| Thu 5 Nov | Chrudim 01:29 | No data | — |
| Wed 4 Nov | Chrudim 01:29 | No data | — |
| Tue 3 Nov | Chrudim 01:29 | No data | — |
| Mon 2 Nov | Chrudim 01:29 | No data | — |
| Sun 1 Nov | Chrudim 01:29 | No data | — |
| Sat 31 Oct | Chrudim 01:29 | No data | — |
| Fri 30 Oct | Chrudim 01:29 | No data | — |
| Thu 29 Oct | Chrudim 01:29 | No data | — |
| Wed 28 Oct | Chrudim 01:30 | No data | — |
| Tue 27 Oct | Chrudim 01:29 | No data | — |
| Mon 26 Oct | Chrudim 01:29 | No data | — |
| Sun 25 Oct | Chrudim 02:29 | No data | — |
| Sat 24 Oct | Chrudim 01:29 | No data | — |
| Fri 23 Oct | Chrudim 01:29 | No data | — |
| Thu 22 Oct | Chrudim 01:29 | No data | — |
| Wed 21 Oct | Chrudim 01:29 | No data | — |
| Tue 20 Oct | Chrudim 01:29 | No data | — |
| Mon 19 Oct | Chrudim 01:29 | No data | — |
| Sun 18 Oct | Chrudim 01:29 | No data | — |
| Sat 17 Oct | Chrudim 01:29 | No data | — |
| Fri 16 Oct | Chrudim 01:29 | No data | — |
| Thu 15 Oct | Chrudim 01:29 | No data | — |
| Wed 14 Oct | Chrudim 01:29 | No data | — |
| Tue 13 Oct | Chrudim 01:29 | No data | — |
| Mon 12 Oct | Chrudim 01:29 | No data | — |
| Sun 11 Oct | Chrudim 01:30 | No data | — |
| Sat 10 Oct | Chrudim 01:29 | No data | — |