Os 5737 5737 Vrchlabí – Trutnov hl. n.

View line Os 5737

Vrchlabí 07:56 → Trutnov hl. n. 08:39 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 12 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 07:56 from Vrchlabí · Fri 6 Nov

Full trip card
Next departure 07:56 today · Vrchlabí
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

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

  • Early 8% · 3
  • On time 93% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% 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, 40 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í
07:56on time on time
Podhůří
07:59≈ on time ≈ on time
Kunčice nad Labem
08:03 / 08:04≈ on time ≈ on time
Klášterská Lhota
08:08≈ on time ≈ on time
Prosečné
08:12≈ on time ≈ on time
Hostinné město
08:14 / 08:15≈ on time ≈ on time
Hostinné
08:17≈ on time ≈ on time
Chotěvice
08:21≈ 1 min early ≈ +1 min
Pilníkov
08:26 / 08:27≈ 1 min early ≈ +1 min
Vlčice
08:30≈ 1 min early ≈ +1 min
Trutnov-Volanov
08:35≈ 1 min early ≈ +1 min
Trutnov hl. n.
08:39on time +1 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
Thu 5 NovTrutnov hl. n. 08:39No data—
Wed 4 NovTrutnov hl. n. 08:39No data—
Tue 3 NovTrutnov hl. n. 08:39No data—
Mon 2 NovTrutnov hl. n. 08:39No data—
Fri 30 OctTrutnov hl. n. 08:40No data—
Thu 29 OctTrutnov hl. n. 08:40No data—
Tue 27 OctTrutnov hl. n. 08:40No data—
Mon 26 OctTrutnov hl. n. 08:40No data—
Fri 23 OctTrutnov hl. n. 08:41No data—
Thu 22 OctTrutnov hl. n. 08:41No data—
Wed 21 OctTrutnov hl. n. 08:40No data—
Tue 20 OctTrutnov hl. n. 08:40No data—
Mon 19 OctTrutnov hl. n. 08:40No data—
Fri 16 OctTrutnov hl. n. 08:41No data—
Thu 15 OctTrutnov hl. n. 08:40No data—
Wed 14 OctTrutnov hl. n. 08:40No data—
Tue 13 OctTrutnov hl. n. 08:40No data—
Mon 12 OctTrutnov hl. n. 08:40No data—
Fri 9 OctTrutnov hl. n. 08:40No data—
Thu 8 OctTrutnov hl. n. 08:40No data—
Wed 7 OctTrutnov hl. n. 08:40No data—
Tue 6 OctTrutnov hl. n. 08:40No data—
Mon 5 Oct— 08:55+1 min+1 min
Fri 2 Oct— 08:55+1 min+1 min
Thu 1 Oct— 08:52−1 min—
Wed 30 Sept— 08:52−1 min—
Tue 29 Sept— 08:530 min+2 min
Fri 25 Sept— 08:52−1 min+1 min
Thu 24 Sept— 08:540 min—
Wed 23 Sept— 08:54+1 min+2 min