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