Os 25051 25051 Moravany – Chrudim
Alerts for train 25051
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 25051.
✓ Today’s run finished
Today, last fix heading to Chrudim at 15:34 No data
- Moravany15:04
- Bořice15:08
- Hrochův Týnec15:12
- Úhřetice15:20
- Tuněchody15:22
- Chrudim město15:29
- Chrudim15:35
Next service: tomorrow 15:04 from Moravany · Sat 14 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
- Wed 2 Sept Max en route +19 min · last fix heading to — +17 min
- Thu 24 Sept Max en route +17 min · last fix heading to — +15 min
- Fri 4 Sept Max en route +18 min · last fix heading to — +14 min
- Mon 31 Aug Max en route +14 min · last fix heading to — +12 min
- Sun 23 Aug Max en route +16 min · last fix heading to — +12 min
Distribution · 90 days
51 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 53% · 27
- 3–10 min 35% · 18
- 10–30 min 12% · 6
- 30+ min 0% · 0
On-time by weekday
- 63% M n=8
- 57% T n=7
- 57% W n=7
- 29% T n=7
- 43% F n=7
- 57% S n=7
- 63% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 51 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:04 | +4 min | +14 min | |
| 15:08 | ≈ +4 min | ≈ +13 min | |
| 15:12 / 15:14 | ≈ +3 min | ≈ +13 min | |
| 15:18 | ≈ +3 min | ≈ +12 min | |
| 15:20 | ≈ +3 min | ≈ +11 min | |
| 15:22 | ≈ +3 min | ≈ +11 min | |
| 15:29 / 15:32 | ≈ +2 min | ≈ +11 min | |
| 15:35 | +2 min | +10 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 |
|---|---|---|---|
| Fri 13 Nov | Chrudim 15:34 | No data | — |
| Thu 12 Nov | Chrudim 15:34 | No data | — |
| Wed 11 Nov | Chrudim 15:34 | No data | — |
| Tue 10 Nov | Chrudim 15:34 | No data | — |
| Mon 9 Nov | Chrudim 15:34 | No data | — |
| Sun 8 Nov | Chrudim 15:34 | No data | — |
| Sat 7 Nov | Chrudim 15:35 | No data | — |
| Fri 6 Nov | Chrudim 15:34 | No data | — |
| Thu 5 Nov | Chrudim 15:34 | No data | — |
| Wed 4 Nov | Chrudim 15:35 | No data | — |
| Tue 3 Nov | Chrudim 15:34 | No data | — |
| Mon 2 Nov | Chrudim 15:34 | No data | — |
| Sun 1 Nov | Chrudim 15:36 | No data | — |
| Sat 31 Oct | Chrudim 15:36 | No data | — |
| Fri 30 Oct | Chrudim 15:36 | No data | — |
| Thu 29 Oct | Chrudim 15:36 | No data | — |
| Wed 28 Oct | Chrudim 15:36 | No data | — |
| Tue 27 Oct | Chrudim 15:36 | No data | — |
| Mon 26 Oct | Chrudim 15:36 | No data | — |
| Sun 25 Oct | Chrudim 15:36 | No data | — |
| Sat 24 Oct | Chrudim 15:36 | No data | — |
| Fri 23 Oct | Chrudim 15:36 | No data | — |
| Thu 22 Oct | Chrudim 15:36 | No data | — |
| Wed 21 Oct | Chrudim 15:36 | No data | — |
| Tue 20 Oct | Chrudim 15:36 | No data | — |
| Mon 19 Oct | Chrudim 15:36 | No data | — |
| Sun 18 Oct | Chrudim 15:36 | No data | — |
| Sat 17 Oct | Chrudim 15:36 | No data | — |
| Fri 16 Oct | Chrudim 15:36 | No data | — |
| Thu 15 Oct | Chrudim 15:36 | No data | — |