Os 5161 5161 Týniště nad Orlicí – Vamberk
Alerts for train 5161
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 5161.
Running now · updated 05:26
Position estimated from the timetable
Between Kostelec nad Orlicí and Doudleby nad Orlicí No data
Estimated arrival at Vamberk 05:40 · 7 km/h
- Týniště nad Orlicí05:08
- Lípa nad Orlicí05:11
- Čestice05:14
- Kostelec nad Orlicí město05:20
- Kostelec nad Orlicí05:22
- Doudleby nad Orlicí05:26
- Vamberk05:40
Last 30 days
Arrival delay at Vamberk, 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 +4 min · last fix heading to — +4 min
- Tue 22 Sept Max en route +14 min · last fix heading to — +4 min
- Wed 23 Sept Max en route +14 min · last fix heading to — +3 min
Distribution · 90 days
31 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 28
- 3–10 min 10% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 83% T n=6
- 83% W n=6
- 83% T n=6
- 100% F n=7
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 31 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 | Today |
|---|---|---|---|---|
| 05:08 | on time | on time | Passed | |
| 05:11 | ≈ on time | ≈ on time | Passed | |
| 05:14 | ≈ on time | ≈ +1 min | Passed | |
| 05:17 / 05:18 | ≈ on time | ≈ +1 min | Passed | |
| 05:20 / 05:21 | ≈ on time | ≈ +1 min | Passed | |
| 05:22 | ≈ on time | ≈ +1 min | Passed | |
| 05:26 / 05:36 | ≈ on time | ≈ +1 min | ||
| 05:40 | on time | +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 |
|---|---|---|---|
| Wed 18 Nov | Doudleby nad Orlicí 05:24Partial coverage | No data | — |
| Mon 16 Nov | Vamberk 05:40 | No data | — |
| Fri 13 Nov | Vamberk 05:39 | No data | — |
| Thu 12 Nov | Vamberk 05:39 | No data | — |
| Wed 11 Nov | Vamberk 05:39 | No data | — |
| Tue 10 Nov | Vamberk 05:39 | No data | — |
| Mon 9 Nov | Vamberk 05:39 | No data | — |
| Fri 6 Nov | Vamberk 05:39 | No data | — |
| Thu 5 Nov | Vamberk 05:39 | No data | — |
| Wed 4 Nov | Vamberk 05:39 | No data | — |
| Tue 3 Nov | Vamberk 05:40 | No data | — |
| Mon 2 Nov | Vamberk 05:39 | No data | — |
| Fri 30 Oct | Vamberk 05:41 | No data | — |
| Thu 29 Oct | Vamberk 05:41 | No data | — |
| Tue 27 Oct | Vamberk 05:41 | No data | — |
| Mon 26 Oct | Vamberk 05:41 | No data | — |
| Fri 23 Oct | Vamberk 05:41 | No data | — |
| Thu 22 Oct | Vamberk 05:41 | No data | — |
| Wed 21 Oct | Vamberk 05:41 | No data | — |
| Tue 20 Oct | Vamberk 05:41 | No data | — |
| Mon 19 Oct | Vamberk 05:41 | No data | — |
| Fri 16 Oct | Vamberk 05:41 | No data | — |
| Thu 15 Oct | Vamberk 05:41 | No data | — |
| Wed 14 Oct | Vamberk 05:41 | No data | — |
| Tue 13 Oct | Vamberk 05:41 | No data | — |
| Mon 12 Oct | Vamberk 05:41 | No data | — |
| Fri 9 Oct | Vamberk 05:41 | No data | — |
| Thu 8 Oct | Vamberk 05:41 | No data | — |
| Wed 7 Oct | Vamberk 05:41 | No data | — |
| Tue 6 Oct | Vamberk 05:42 | No data | — |