Os 5746 5746 Trutnov hl. n. – Vrchlabí

View line Os 5746

Trutnov hl. n. 19:22 → Vrchlabí 20:06 Mon, Tue, Wed, Thu, Fri 0 h 44 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 19:22 from Trutnov hl. n. · Mon 16 Nov

Next departure 19:22 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
67%
22/33 runs under 3 min
RT coverage: 33 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
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

  • Fri 2 Oct Max en route +6 min · last fix heading to — +5 min
  • Thu 1 Oct Max en route +6 min · last fix heading to — +5 min
  • Thu 24 Sept Max en route +7 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +7 min · last fix heading to — +5 min
  • Fri 18 Sept Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 22
  • 3–10 min 33% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 71% T n=7
  • 71% W n=7
  • 57% T n=7
  • 43% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
19:22+1 min +7 min
19:25≈ +1 min ≈ +7 min
19:30≈ +1 min ≈ +6 min
19:34 / 19:35≈ +1 min ≈ +6 min
19:39≈ +1 min ≈ +6 min
19:43 / 19:44≈ +1 min ≈ +5 min
19:46≈ +1 min ≈ +5 min
19:49≈ +1 min ≈ +5 min
19:53≈ +1 min ≈ +5 min
19:58 / 19:59≈ +1 min ≈ +5 min
20:02≈ on time ≈ +5 min
20:06on time +5 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

DateLast stopFinalMax
Fri 13 NovVrchlabí 20:07No data—
Thu 12 NovVrchlabí 20:07No data—
Wed 11 NovVrchlabí 20:07No data—
Tue 10 NovVrchlabí 20:07No data—
Mon 9 NovVrchlabí 20:07No data—
Fri 6 NovVrchlabí 20:07No data—
Thu 5 NovVrchlabí 20:07No data—
Wed 4 NovVrchlabí 20:07No data—
Tue 3 NovVrchlabí 20:07No data—
Mon 2 NovVrchlabí 20:07No data—
Fri 30 OctVrchlabí 20:07No data—
Thu 29 OctVrchlabí 20:07No data—
Tue 27 OctVrchlabí 20:08No data—
Mon 26 OctVrchlabí 20:07No data—
Fri 23 OctVrchlabí 20:07No data—
Thu 22 OctVrchlabí 20:07No data—
Wed 21 OctVrchlabí 20:07No data—
Tue 20 OctVrchlabí 20:07No data—
Mon 19 OctVrchlabí 20:07No data—
Fri 16 OctVrchlabí 20:07No data—
Thu 15 OctVrchlabí 20:07No data—
Wed 14 OctVrchlabí 20:07No data—
Tue 13 OctVrchlabí 20:07No data—
Mon 12 OctVrchlabí 20:08No data—
Fri 9 OctVrchlabí 20:07No data—
Thu 8 OctVrchlabí 20:07No data—
Wed 7 OctVrchlabí 20:07No data—
Tue 6 OctVrchlabí 20:07No data—
Mon 5 OctVrchlabí 20:07No data—
Fri 2 Oct— 20:25+5 min+6 min