Os 5151 5151 Doudleby nad Orlicí – Letohrad
Alerts for train 5151
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 5151.
It has not run yet today
Last recorded run: Thursday 12 November No data
Next service: today 04:35 from Doudleby nad Orlicí · Fri 13 Nov
Last 30 days
Arrival delay at Letohrad, 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 25 Sept Max en route +3 min · last fix heading to — +3 min
- Wed 2 Sept Max en route +4 min · last fix heading to — +3 min
- Mon 17 Aug Max en route +4 min · last fix heading to — +3 min
Distribution · 90 days
35 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 32
- 3–10 min 9% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 86% M n=7
- 100% T n=7
- 86% W n=7
- 100% T n=7
- 86% F n=7
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 35 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 |
|---|---|---|---|
| 04:35 | on time | on time | |
| 04:38 | ≈ on time | ≈ on time | |
| 04:42 / 04:43 | ≈ on time | ≈ on time | |
| 04:45 | ≈ on time | ≈ +1 min | |
| 04:48 / 04:49 | ≈ on time | ≈ +1 min | |
| 04:52 | ≈ on time | ≈ +1 min | |
| 04:58 / 04:59 | ≈ on time | ≈ +1 min | |
| 05:03 | ≈ on time | ≈ +1 min | |
| 05:07 | on time | +2 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 |
|---|---|---|---|
| Thu 12 Nov | Letohrad 05:08 | No data | — |
| Wed 11 Nov | Letohrad 05:08 | No data | — |
| Tue 10 Nov | Letohrad 05:08 | No data | — |
| Mon 9 Nov | Letohrad 05:08 | No data | — |
| Fri 6 Nov | Letohrad 05:08 | No data | — |
| Thu 5 Nov | Letohrad 05:08 | No data | — |
| Wed 4 Nov | Letohrad 05:08 | No data | — |
| Tue 3 Nov | Letohrad 05:09 | No data | — |
| Mon 2 Nov | Letohrad 05:08 | No data | — |
| Fri 30 Oct | Letohrad 05:08 | No data | — |
| Thu 29 Oct | Letohrad 05:08 | No data | — |
| Tue 27 Oct | Letohrad 05:08 | No data | — |
| Mon 26 Oct | Letohrad 05:08 | No data | — |
| Fri 23 Oct | Letohrad 05:08 | No data | — |
| Thu 22 Oct | Letohrad 05:08 | No data | — |
| Wed 21 Oct | Letohrad 05:08 | No data | — |
| Tue 20 Oct | Letohrad 05:08 | No data | — |
| Mon 19 Oct | Letohrad 05:08 | No data | — |
| Fri 16 Oct | Letohrad 05:08 | No data | — |
| Thu 15 Oct | Letohrad 05:08 | No data | — |
| Wed 14 Oct | Letohrad 05:08 | No data | — |
| Tue 13 Oct | Letohrad 05:08 | No data | — |
| Mon 12 Oct | Letohrad 05:08 | No data | — |
| Fri 9 Oct | Letohrad 05:08 | No data | — |
| Thu 8 Oct | Letohrad 05:08 | No data | — |
| Wed 7 Oct | Letohrad 05:08 | No data | — |
| Tue 6 Oct | Letohrad 05:08 | No data | — |
| Mon 5 Oct | — 05:23 | 0 min | — |
| Fri 2 Oct | — 05:20 | −1 min | — |
| Thu 1 Oct | — 05:21 | 0 min | +1 min |