Os 5738 5738 Trutnov hl. n. – Vrchlabí

View line Os 5738

Trutnov hl. n. 11:48 → Vrchlabí 12:29 Mon, Tue, Wed, Thu, Fri 0 h 41 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Vrchlabí at 12:29 No data

  1. Trutnov hl. n.11:48
  2. Vlčice11:55
  3. Chotěvice12:03
  4. Hostinné město12:10
  5. Prosečné12:13
  6. Kunčice nad Labem12:21
  7. Vrchlabí12:29

Next service: Monday 11:48 from Trutnov hl. n. · Mon 9 Nov

Next departure 11:48 Monday · Trutnov hl. n.
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
85%
34/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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

  • Wed 12 Aug Max en route +8 min · last fix heading to — +6 min
  • Thu 24 Sept Max en route +8 min · last fix heading to — +4 min
  • Thu 10 Sept Max en route +7 min · last fix heading to — +4 min
  • Tue 29 Sept Max en route +4 min · last fix heading to — +3 min
  • Mon 17 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 34
  • 3–10 min 15% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 75% T n=8
  • 88% W n=8
  • 75% 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
11:48on time +5 min
11:51≈ on time ≈ +5 min
11:55≈ on time ≈ +5 min
11:58 / 11:59≈ on time ≈ +4 min
12:03≈ on time ≈ +4 min
12:07 / 12:08≈ on time ≈ +4 min
12:10≈ on time ≈ +3 min
12:13≈ on time ≈ +3 min
12:17≈ on time ≈ +3 min
12:21 / 12:22≈ on time ≈ +3 min
12:26≈ on time ≈ +3 min
12:29on time +3 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 6 NovVrchlabí 12:29No data—
Thu 5 NovVrchlabí 12:29No data—
Wed 4 NovVrchlabí 12:29No data—
Tue 3 NovVrchlabí 12:29No data—
Mon 2 NovVrchlabí 12:29No data—
Fri 30 OctVrchlabí 12:31No data—
Thu 29 OctVrchlabí 12:31No data—
Tue 27 OctVrchlabí 12:31No data—
Mon 26 OctVrchlabí 12:31No data—
Fri 23 OctVrchlabí 12:31No data—
Thu 22 OctVrchlabí 12:31No data—
Wed 21 OctVrchlabí 12:31No data—
Tue 20 OctVrchlabí 12:31No data—
Mon 19 OctVrchlabí 12:31No data—
Fri 16 OctVrchlabí 12:31No data—
Thu 15 OctVrchlabí 12:31No data—
Wed 14 OctVrchlabí 12:31No data—
Tue 13 OctVrchlabí 12:31No data—
Mon 12 OctVrchlabí 12:31No data—
Fri 9 OctVrchlabí 12:31No data—
Thu 8 OctVrchlabí 12:31No data—
Wed 7 OctVrchlabí 12:31No data—
Tue 6 OctVrchlabí 12:31No data—
Mon 5 Oct— 12:45+2 min+4 min
Fri 2 Oct— 12:440 min+2 min
Thu 1 Oct— 12:46+2 min+3 min
Wed 30 Sept— 12:440 min+1 min
Tue 29 Sept— 12:46+3 min+4 min
Fri 25 Sept— 12:440 min+2 min
Thu 24 Sept— 12:50+4 min+8 min