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