Os 5744 5744 Trutnov hl. n. – Vrchlabí
Alerts for train 5744
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 5744.
It has not run yet today
Last recorded run: Saturday 14 November No data
Next service: today 17:48 from Trutnov hl. n. · Sun 15 Nov
Last 30 days
Arrival delay at Vrchlabí, 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 23 Sept Max en route +11 min · last fix heading to — +11 min
- Wed 30 Sept Max en route +4 min · last fix heading to — +4 min
- Thu 24 Sept Max en route +4 min · last fix heading to — +3 min
- Sat 19 Sept Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
48 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 44
- 3–10 min 6% · 3
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=7
- 71% W n=7
- 86% T n=7
- 100% F n=7
- 86% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 49 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 |
|---|---|---|---|
| 17:48 | on time | +3 min | |
| 17:51 | ≈ on time | ≈ +3 min | |
| 17:55 | ≈ on time | ≈ +3 min | |
| 17:58 / 17:59 | ≈ on time | ≈ +2 min | |
| 18:03 | ≈ on time | ≈ +2 min | |
| 18:07 / 18:08 | ≈ on time | ≈ +2 min | |
| 18:10 | ≈ on time | ≈ +2 min | |
| 18:13 | ≈ on time | ≈ +2 min | |
| 18:17 | ≈ on time | ≈ +2 min | |
| 18:21 / 18:22 | ≈ on time | ≈ +2 min | |
| 18:26 | ≈ on time | ≈ +2 min | |
| 18:29 | 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 |
|---|---|---|---|
| Sat 14 Nov | Vrchlabí 18:29 | No data | — |
| Fri 13 Nov | Vrchlabí 18:29 | No data | — |
| Thu 12 Nov | Vrchlabí 18:29 | No data | — |
| Wed 11 Nov | Vrchlabí 18:29 | No data | — |
| Tue 10 Nov | Vrchlabí 18:29 | No data | — |
| Mon 9 Nov | Vrchlabí 18:29 | No data | — |
| Sun 8 Nov | Vrchlabí 18:29 | No data | — |
| Sat 7 Nov | Vrchlabí 18:29 | No data | — |
| Fri 6 Nov | Vrchlabí 18:29 | No data | — |
| Thu 5 Nov | Vrchlabí 18:29 | No data | — |
| Wed 4 Nov | Vrchlabí 18:29 | No data | — |
| Tue 3 Nov | Vrchlabí 18:29 | No data | — |
| Mon 2 Nov | Vrchlabí 18:29 | No data | — |
| Sun 1 Nov | Vrchlabí 18:29 | No data | — |
| Sat 31 Oct | Vrchlabí 18:31 | No data | — |
| Fri 30 Oct | Vrchlabí 18:31 | No data | — |
| Thu 29 Oct | Vrchlabí 18:31 | No data | — |
| Wed 28 Oct | Vrchlabí 18:31 | No data | — |
| Tue 27 Oct | Vrchlabí 18:31 | No data | — |
| Mon 26 Oct | Vrchlabí 18:31 | No data | — |
| Sun 25 Oct | Vrchlabí 18:31 | No data | — |
| Sat 24 Oct | Vrchlabí 18:31 | No data | — |
| Fri 23 Oct | Vrchlabí 18:31 | No data | — |
| Thu 22 Oct | Vrchlabí 18:31 | No data | — |
| Wed 21 Oct | Vrchlabí 18:31 | No data | — |
| Tue 20 Oct | Vrchlabí 18:31 | No data | — |
| Mon 19 Oct | Vrchlabí 18:31 | No data | — |
| Sun 18 Oct | Vrchlabí 18:31 | No data | — |
| Sat 17 Oct | Vrchlabí 18:31 | No data | — |
| Fri 16 Oct | Vrchlabí 18:31 | No data | — |