Os 5732 5732 Trutnov hl. n. – Vrchlabí

View line Os 5732

Trutnov hl. n. 05:51 → Vrchlabí 06:34 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 05:51 from Trutnov hl. n. · Mon 16 Nov

Full trip card
Next departure 05:51 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
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 28 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

Distribution · 90 days

24 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 24 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.
05:51on time on time
Trutnov-Volanov
05:54≈ on time ≈ on time
Vlčice
05:58≈ on time ≈ on time
Pilníkov
06:01 / 06:02≈ on time ≈ on time
Chotěvice
06:06≈ on time ≈ on time
Hostinné
06:11 / 06:12≈ on time ≈ on time
Hostinné město
06:15≈ on time ≈ on time
Prosečné
06:18≈ on time ≈ on time
Klášterská Lhota
06:21≈ on time ≈ on time
Kunčice nad Labem
06:26 / 06:27≈ on time ≈ on time
Podhůří
06:30≈ on time ≈ on time
Vrchlabí
06:34on 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 13 NovVrchlabí 06:34No data—
Thu 12 NovVrchlabí 06:34No data—
Wed 11 NovVrchlabí 06:34No data—
Tue 10 NovVrchlabí 06:34No data—
Mon 9 NovVrchlabí 06:34No data—
Fri 6 NovVrchlabí 06:34No data—
Thu 5 NovVrchlabí 06:34No data—
Wed 4 NovVrchlabí 06:34No data—
Tue 3 NovVrchlabí 06:34No data—
Mon 2 NovVrchlabí 06:34No data—
Fri 30 OctVrchlabí 06:35No data—
Thu 29 OctVrchlabí 06:35No data—
Tue 27 OctVrchlabí 06:35No data—
Mon 26 OctVrchlabí 06:35No data—
Fri 23 OctVrchlabí 06:36No data—
Thu 22 OctVrchlabí 06:35No data—
Wed 21 OctVrchlabí 06:35No data—
Tue 20 OctVrchlabí 06:35No data—
Mon 19 OctVrchlabí 06:35No data—
Fri 16 OctVrchlabí 06:35No data—
Thu 15 OctVrchlabí 06:35No data—
Wed 14 OctVrchlabí 06:35No data—
Tue 13 OctVrchlabí 06:35No data—
Mon 12 OctVrchlabí 06:35No data—
Fri 9 OctVrchlabí 06:35No data—
Thu 8 OctVrchlabí 06:35No data—
Wed 7 OctVrchlabí 06:35No data—
Tue 6 OctVrchlabí 06:35No data—
Mon 5 Oct— 06:48−1 min+2 min
Fri 2 Oct— 06:490 min—