Os 5741 5741 Vrchlabí – Trutnov hl. n.

View line Os 5741

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

✓ Today’s run finished

Today, last fix heading to Trutnov hl. n. at 12:13 No data

  1. Vrchlabí11:26
  2. Kunčice nad Labem11:33
  3. Prosečné11:41
  4. Hostinné11:46
  5. Chotěvice11:51
  6. Vlčice12:03
  7. Trutnov hl. n.12:12

Next service: Monday 11:26 from Vrchlabí · Mon 9 Nov

Next departure 11:26 Monday · Vrchlabí
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
88%
35/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 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

Worst days

  • Thu 24 Sept Max en route +7 min · last fix heading to — +6 min
  • Wed 12 Aug Max en route +8 min · last fix heading to — +5 min
  • Mon 5 Oct Max en route +3 min · last fix heading to — +3 min
  • Tue 25 Aug Max en route +3 min · last fix heading to — +3 min
  • Tue 11 Aug Max en route +6 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 3% · 1
  • On time 85% · 34
  • 3–10 min 13% · 5
  • 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
  • 88% 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:26on time +2 min
11:29≈ on time ≈ +2 min
11:33 / 11:34≈ on time ≈ +2 min
11:38≈ on time ≈ +2 min
11:41≈ on time ≈ +2 min
11:44≈ on time ≈ +2 min
11:46 / 11:47≈ on time ≈ +2 min
11:51≈ on time ≈ +2 min
11:56 / 12:00≈ on time ≈ +2 min
12:03≈ on time ≈ +2 min
12:08≈ on time ≈ +3 min
12:12on 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 NovTrutnov hl. n. 12:13No data—
Thu 5 NovTrutnov hl. n. 12:13No data—
Wed 4 NovTrutnov hl. n. 12:13No data—
Tue 3 NovTrutnov hl. n. 12:13No data—
Mon 2 NovTrutnov hl. n. 12:13No data—
Fri 30 OctTrutnov hl. n. 12:13No data—
Thu 29 OctTrutnov hl. n. 12:13No data—
Tue 27 OctTrutnov hl. n. 12:13No data—
Mon 26 OctTrutnov hl. n. 12:13No data—
Fri 23 OctTrutnov hl. n. 12:13No data—
Thu 22 OctTrutnov hl. n. 12:13No data—
Wed 21 OctTrutnov hl. n. 12:13No data—
Tue 20 OctTrutnov hl. n. 12:13No data—
Mon 19 OctTrutnov hl. n. 12:13No data—
Fri 16 OctTrutnov hl. n. 12:13No data—
Thu 15 OctTrutnov hl. n. 12:13No data—
Wed 14 OctTrutnov hl. n. 12:13No data—
Tue 13 OctTrutnov hl. n. 12:13No data—
Mon 12 OctTrutnov hl. n. 12:13No data—
Fri 9 OctTrutnov hl. n. 12:13No data—
Thu 8 OctTrutnov hl. n. 12:13No data—
Wed 7 OctTrutnov hl. n. 12:13No data—
Tue 6 OctTrutnov hl. n. 12:13No data—
Mon 5 Oct— 12:29+3 min+3 min
Fri 2 Oct— 12:25−1 min+2 min
Thu 1 Oct— 12:270 min+2 min
Wed 30 Sept— 12:260 min+1 min
Tue 29 Sept— 12:260 min—
Fri 25 Sept— 12:270 min—
Thu 24 Sept— 12:33+6 min+7 min