Os 2632 2632 Liberec – Harrachov

View line Os 2632

Liberec 15:35 → Harrachov 16:52 Daily 1 h 17 min · 25 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Harrachov at 16:53 No data

  1. Liberec15:35
  2. Proseč nad Nisou15:45
  3. Jablonec nad Nisou zastávka15:59
  4. Smržovka16:11
  5. Tanvald zastávka16:20
  6. Dolní Polubný16:36
  7. Harrachov16:52

Next service: tomorrow 15:35 from Liberec · Mon 16 Nov

Next departure 15:35 tomorrow · Liberec
On-time · 30 days
—
Too little data (0/25 runs with data)
RT coverage: 0 full · 0 partial · 25 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 5 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Harrachov, 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 5 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
15:35on time +1 min
15:38≈ on time ≈ +1 min
15:41≈ on time ≈ +1 min
15:42≈ on time ≈ +1 min
15:45≈ on time ≈ +1 min
15:50≈ on time ≈ +1 min
15:55 / 15:56≈ on time ≈ +1 min
15:57≈ on time ≈ +1 min
15:59≈ on time ≈ +1 min
16:00≈ on time ≈ +1 min
16:02≈ on time ≈ +1 min
16:06≈ on time ≈ +1 min
16:11 / 16:12≈ on time ≈ +1 min
16:13≈ +1 min ≈ +1 min
16:14≈ +1 min ≈ +1 min
16:17≈ on time ≈ +1 min
16:20≈ on time ≈ +1 min
16:25 / 16:28≈ on time ≈ +1 min
16:31 / 16:32≈ on time ≈ +1 min
16:34≈ on time ≈ +1 min
16:36≈ on time ≈ +1 min
16:38≈ on time ≈ +1 min
16:40≈ on time ≈ +1 min
16:43 / 16:44≈ on time ≈ +1 min
16:52on time +2 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
Sun 15 NovHarrachov 16:53No data—
Sat 14 NovHarrachov 16:53No data—
Fri 13 NovHarrachov 16:53No data—
Thu 12 NovHarrachov 16:53No data—
Wed 11 NovHarrachov 16:53No data—
Tue 10 NovHarrachov 16:53No data—
Mon 9 NovHarrachov 16:53No data—
Sun 8 NovHarrachov 16:53No data—
Sat 7 NovHarrachov 16:53No data—
Fri 6 NovHarrachov 16:53No data—
Thu 5 NovHarrachov 16:53No data—
Wed 4 NovHarrachov 16:53No data—
Tue 3 NovHarrachov 16:53No data—
Mon 2 NovHarrachov 16:53No data—
Sun 1 NovHarrachov 16:53No data—
Sat 31 OctHarrachov 16:53No data—
Fri 30 OctHarrachov 16:53No data—
Thu 29 OctHarrachov 16:53No data—
Tue 27 OctHarrachov 16:53No data—
Mon 26 OctHarrachov 16:53No data—
Fri 23 OctHarrachov 16:53No data—
Thu 22 OctHarrachov 16:53No data—
Wed 21 OctHarrachov 16:53No data—
Tue 20 OctHarrachov 16:53No data—
Mon 19 OctHarrachov 16:53No data—
Fri 16 OctHarrachov 16:53No data—
Thu 15 OctHarrachov 16:53No data—
Wed 14 OctHarrachov 16:53No data—
Tue 13 OctHarrachov 16:53No data—
Mon 12 OctHarrachov 16:53No data—