Os 5745 5745 Vrchlabí – Trutnov hl. n.

View line Os 5745

Vrchlabí 15:26 → Trutnov hl. n. 16:12 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 12 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 13 November No data

Next service: tomorrow 15:26 from Vrchlabí · Mon 16 Nov

Full trip card
Next departure 15:26 tomorrow · Vrchlabí
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%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 28 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Trutnov hl. n., 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

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

  • Early 6% · 2
  • On time 94% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% 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, 34 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
Vrchlabí
15:26on time on time
Podhůří
15:29≈ on time ≈ on time
Kunčice nad Labem
15:33 / 15:34≈ on time ≈ on time
Klášterská Lhota
15:38≈ on time ≈ on time
Prosečné
15:41≈ on time ≈ on time
Hostinné město
15:44≈ on time ≈ on time
Hostinné
15:46 / 15:47≈ on time ≈ on time
Chotěvice
15:51≈ 1 min early ≈ on time
Pilníkov
15:56 / 16:00≈ 1 min early ≈ on time
Vlčice
16:03≈ 1 min early ≈ on time
Trutnov-Volanov
16:08≈ 1 min early ≈ on time
Trutnov hl. n.
16:121 min early 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 NovTrutnov hl. n. 16:13No data—
Thu 12 NovTrutnov hl. n. 16:13No data—
Wed 11 NovTrutnov hl. n. 16:13No data—
Tue 10 NovTrutnov hl. n. 16:13No data—
Mon 9 NovTrutnov hl. n. 16:13No data—
Fri 6 NovTrutnov hl. n. 16:13No data—
Thu 5 NovTrutnov hl. n. 16:13No data—
Wed 4 NovTrutnov hl. n. 16:13No data—
Tue 3 NovTrutnov hl. n. 16:13No data—
Mon 2 NovTrutnov hl. n. 16:13No data—
Fri 30 OctTrutnov hl. n. 16:13No data—
Thu 29 OctTrutnov hl. n. 16:13No data—
Tue 27 OctTrutnov hl. n. 16:13No data—
Mon 26 OctTrutnov hl. n. 16:13No data—
Fri 23 OctTrutnov hl. n. 16:13No data—
Thu 22 OctTrutnov hl. n. 16:13No data—
Wed 21 OctTrutnov hl. n. 16:13No data—
Tue 20 OctTrutnov hl. n. 16:13No data—
Mon 19 OctTrutnov hl. n. 16:13No data—
Fri 16 OctTrutnov hl. n. 16:13No data—
Thu 15 OctTrutnov hl. n. 16:13No data—
Wed 14 OctTrutnov hl. n. 16:13No data—
Tue 13 OctTrutnov hl. n. 16:13No data—
Mon 12 OctTrutnov hl. n. 16:13No data—
Fri 9 OctTrutnov hl. n. 16:13No data—
Thu 8 OctTrutnov hl. n. 16:13No data—
Wed 7 OctTrutnov hl. n. 16:13No data—
Tue 6 OctTrutnov hl. n. 16:13No data—
Mon 5 Oct— 16:23−1 min—
Fri 2 Oct— 16:25−1 min+3 min