Os 5734 5734 Trutnov hl. n. – Vrchlabí

View line Os 5734

Trutnov hl. n. 06:58 → Vrchlabí 07:47 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 06:58 from Trutnov hl. n. · Mon 9 Nov

Full trip card
Next departure 06:58 tomorrow · Trutnov hl. n.
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

  • Tue 15 Sept Max en route +5 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 0% · 0
  • On time 97% · 38
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 88% T n=8
  • 100% W n=8
  • 100% 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 (12 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.

StopSched.Usually 9 days in 10
Trutnov hl. n.
06:58on time on time
Trutnov-Volanov
07:01≈ on time ≈ on time
Vlčice
07:05≈ on time ≈ on time
Pilníkov
07:08 / 07:13≈ on time ≈ on time
Chotěvice
07:17≈ on time ≈ on time
Hostinné
07:22 / 07:25≈ on time ≈ on time
Hostinné město
07:28≈ on time ≈ on time
Prosečné
07:31≈ on time ≈ on time
Klášterská Lhota
07:34≈ on time ≈ on time
Kunčice nad Labem
07:39 / 07:40≈ on time ≈ on time
Podhůří
07:43≈ on time ≈ on time
Vrchlabí
07:47on time on time

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

DateLast stopFinalMax
Fri 6 NovVrchlabí 07:48No data—
Thu 5 NovVrchlabí 07:48No data—
Wed 4 NovVrchlabí 07:48No data—
Tue 3 NovVrchlabí 07:48No data—
Mon 2 NovVrchlabí 07:48No data—
Fri 30 OctVrchlabí 07:48No data—
Thu 29 OctVrchlabí 07:48No data—
Tue 27 OctVrchlabí 07:48No data—
Mon 26 OctVrchlabí 07:48No data—
Fri 23 OctVrchlabí 07:48No data—
Thu 22 OctVrchlabí 07:48No data—
Wed 21 OctVrchlabí 07:48No data—
Tue 20 OctVrchlabí 07:48No data—
Mon 19 OctVrchlabí 07:48No data—
Fri 16 OctVrchlabí 07:48No data—
Thu 15 OctVrchlabí 07:49No data—
Wed 14 OctVrchlabí 07:48No data—
Tue 13 OctVrchlabí 07:48No data—
Mon 12 OctVrchlabí 07:48No data—
Fri 9 OctVrchlabí 07:48No data—
Thu 8 OctVrchlabí 07:48No data—
Wed 7 OctVrchlabí 07:48No data—
Tue 6 OctVrchlabí 07:48No data—
Mon 5 Oct— 08:03+1 min+3 min
Fri 2 Oct— 08:020 min+3 min
Thu 1 Oct— 08:01−1 min+2 min
Wed 30 Sept— 08:010 min+2 min
Tue 29 Sept— 08:010 min+1 min
Fri 25 Sept— 08:01−1 min+2 min
Thu 24 Sept— 08:00−1 min+3 min