Os 15002 15002 Choceň – Litomyšl
Alerts for train 15002
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 15002.
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 06:05 from Choceň · Mon 9 Nov
Last 30 days
Arrival delay at Litomyšl, 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 +6 min · last fix heading to — +3 min
Distribution · 90 days
39 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 15% · 6
- On time 82% · 32
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 100% T n=8
- 100% W n=8
- 88% T n=8
- 100% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 39 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 |
|---|---|---|---|
| 06:05 | on time | +2 min | |
| 06:07 | ≈ on time | ≈ +2 min | |
| 06:10 | ≈ on time | ≈ +2 min | |
| 06:13 / 06:14 | ≈ on time | ≈ +1 min | |
| 06:17 / 06:18 | ≈ on time | ≈ +1 min | |
| 06:23 | ≈ on time | ≈ +1 min | |
| 06:26 | ≈ on time | ≈ +1 min | |
| 06:28 | ≈ on time | ≈ +1 min | |
| 06:30 | ≈ on time | ≈ +1 min | |
| 06:33 | ≈ on time | ≈ +1 min | |
| 06:35 | ≈ on time | ≈ +1 min | |
| 06:37 | ≈ 1 min early | ≈ +1 min | |
| 06:39 | ≈ 1 min early | ≈ +1 min | |
| 06:42 | 1 min early | +1 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 6 Nov | Litomyšl 06:43 | No data | — |
| Thu 5 Nov | Litomyšl 06:43 | No data | — |
| Wed 4 Nov | Litomyšl 06:43 | No data | — |
| Tue 3 Nov | Litomyšl 06:43 | No data | — |
| Mon 2 Nov | Litomyšl 06:43 | No data | — |
| Fri 30 Oct | Litomyšl 06:43 | No data | — |
| Thu 29 Oct | Litomyšl 06:43 | No data | — |
| Tue 27 Oct | Litomyšl 06:43 | No data | — |
| Mon 26 Oct | Litomyšl 06:43 | No data | — |
| Fri 23 Oct | Litomyšl 06:43 | No data | — |
| Thu 22 Oct | Litomyšl 06:43 | No data | — |
| Wed 21 Oct | Litomyšl 06:43 | No data | — |
| Tue 20 Oct | Litomyšl 06:43 | No data | — |
| Mon 19 Oct | Litomyšl 06:43 | No data | — |
| Fri 16 Oct | Litomyšl 06:43 | No data | — |
| Thu 15 Oct | Litomyšl 06:43 | No data | — |
| Wed 14 Oct | Litomyšl 06:43 | No data | — |
| Tue 13 Oct | Litomyšl 06:43 | No data | — |
| Mon 12 Oct | Litomyšl 06:43 | No data | — |
| Fri 9 Oct | Litomyšl 06:43 | No data | — |
| Thu 8 Oct | Litomyšl 06:43 | No data | — |
| Wed 7 Oct | Litomyšl 06:43 | No data | — |
| Tue 6 Oct | Litomyšl 06:43 | No data | — |
| Mon 5 Oct | — 06:57 | 0 min | +1 min |
| Fri 2 Oct | — 06:59 | +2 min | +2 min |
| Thu 1 Oct | — 06:58 | 0 min | +2 min |
| Wed 30 Sept | — 06:54 | −2 min | — |
| Tue 29 Sept | — 06:56 | 0 min | +1 min |
| Fri 25 Sept | — 06:57 | 0 min | — |
| Thu 24 Sept | — 06:59 | +3 min | +6 min |