Os 5355 5355 Pardubice hl. n. → Chrudim
Alerts for train 5355
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 5355.
✓ Today’s run finished
Today, last fix heading to Chrudim at 07:45 No data
- Pardubice hl. n.07:23
- Pardubice-Rosice n.L.07:26
- Pardubice závodiště07:31
- Staré Jesenčany07:34
- Medlešice07:38
- Chrudim zastávka07:41
- Chrudim07:44
Next service: tomorrow 07:23 from Pardubice hl. n. · Sun 22 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
- Thu 10 Sept Max en route +17 min · last fix heading to — +17 min
- Tue 29 Sept Max en route +12 min · last fix heading to — +12 min
- Mon 21 Sept Max en route +10 min · last fix heading to — +9 min
- Thu 17 Sept Max en route +10 min · last fix heading to — +9 min
- Fri 11 Sept Max en route +9 min · last fix heading to — +8 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 40% · 16
- 3–10 min 55% · 22
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 43% M n=7
- 20% T n=5
- 0% W n=5
- 0% T n=5
- 0% F n=6
- 100% S n=6
- 100% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 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 |
|---|---|---|---|
| 07:23 | on time | +2 min | |
| 07:26 / 07:29 | ≈ +1 min | ≈ +3 min | |
| 07:31 | ≈ +2 min | ≈ +4 min | |
| 07:34 | ≈ +2 min | ≈ +5 min | |
| 07:38 | ≈ +3 min | ≈ +6 min | |
| 07:41 | ≈ +4 min | ≈ +7 min | |
| 07:44 | +4 min | +8 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 |
|---|---|---|---|
| Sat 21 Nov | Chrudim 07:45 | No data | — |
| Fri 20 Nov | Chrudim 07:44 | No data | — |
| Thu 19 Nov | Chrudim 07:44 | No data | — |
| Wed 18 Nov | Chrudim 07:44 | No data | — |
| Tue 17 Nov | Chrudim 07:44 | No data | — |
| Mon 16 Nov | Chrudim 07:44 | No data | — |
| Sun 15 Nov | Chrudim 07:44 | No data | — |
| Sat 14 Nov | Chrudim 07:44 | No data | — |
| Fri 13 Nov | Chrudim 07:45 | No data | — |
| Thu 12 Nov | Chrudim 07:44 | No data | — |
| Wed 11 Nov | Chrudim 07:44 | No data | — |
| Tue 10 Nov | Chrudim 07:44 | No data | — |
| Mon 9 Nov | Chrudim 07:44 | No data | — |
| Sun 8 Nov | Chrudim 07:44 | No data | — |
| Sat 7 Nov | Chrudim 07:44 | No data | — |
| Fri 6 Nov | Chrudim 07:44 | No data | — |
| Thu 5 Nov | Chrudim 07:44 | No data | — |
| Wed 4 Nov | Chrudim 07:44 | No data | — |
| Tue 3 Nov | Chrudim 07:44 | No data | — |
| Mon 2 Nov | Chrudim 07:44 | No data | — |
| Sun 1 Nov | Chrudim 07:45 | No data | — |
| Sat 31 Oct | Chrudim 07:45 | No data | — |
| Fri 30 Oct | Chrudim 07:45 | No data | — |
| Thu 29 Oct | Chrudim 07:45 | No data | — |
| Wed 28 Oct | Chrudim 07:45 | No data | — |
| Tue 27 Oct | Chrudim 07:45 | No data | — |
| Mon 26 Oct | Chrudim 07:45 | No data | — |
| Sun 25 Oct | Chrudim 07:45 | No data | — |
| Sat 24 Oct | Chrudim 07:45 | No data | — |
| Fri 23 Oct | Chrudim 07:45 | No data | — |