Os 2629 2629 Tanvald – Liberec

View line Os 2629

Tanvald 16:59 → Liberec 17:48 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 18 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:59 from Tanvald · Thu 5 Nov

Next departure 16:59 today · Tanvald
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
79%
31/39 runs under 3 min
RT coverage: 39 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Liberec, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 21 Aug Max en route +7 min · last fix heading to — +6 min
  • Tue 18 Aug Max en route +5 min · last fix heading to — +5 min
  • Fri 14 Aug Max en route +5 min · last fix heading to — +5 min
  • Thu 13 Aug Max en route +6 min · last fix heading to — +5 min
  • Wed 9 Sept Max en route +6 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 31
  • 3–10 min 21% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 88% T n=8
  • 75% W n=8
  • 75% T n=8
  • 63% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
16:59on time +2 min
17:00≈ on time ≈ +2 min
17:02≈ on time ≈ +2 min
17:05≈ on time ≈ +2 min
17:06≈ on time ≈ +2 min
17:11 / 17:12≈ on time ≈ +2 min
17:13≈ on time ≈ +2 min
17:17≈ on time ≈ +2 min
17:19≈ on time ≈ +2 min
17:21≈ on time ≈ +2 min
17:22≈ on time ≈ +2 min
17:26 / 17:27≈ on time ≈ +3 min
17:28≈ on time ≈ +3 min
17:33≈ on time ≈ +3 min
17:37≈ on time ≈ +3 min
17:40 / 17:41≈ on time ≈ +4 min
17:42≈ on time ≈ +4 min
17:48on time +4 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
Wed 4 NovLiberec 17:49No data—
Tue 3 NovLiberec 17:49No data—
Mon 2 NovLiberec 17:49No data—
Fri 30 OctLiberec 17:49No data—
Thu 29 OctLiberec 17:49No data—
Tue 27 OctLiberec 17:49No data—
Mon 26 OctLiberec 17:49No data—
Fri 23 OctLiberec 17:49No data—
Thu 22 OctLiberec 17:49No data—
Wed 21 OctLiberec 17:49No data—
Tue 20 OctLiberec 17:50No data—
Mon 19 OctLiberec 17:49No data—
Fri 16 OctLiberec 17:49No data—
Thu 15 OctLiberec 17:49No data—
Wed 14 OctLiberec 17:49No data—
Tue 13 OctLiberec 17:49No data—
Mon 12 OctLiberec 17:50No data—
Fri 9 OctLiberec 17:49No data—
Thu 8 OctLiberec 17:49No data—
Wed 7 OctLiberec 17:49No data—
Tue 6 OctLiberec 17:49No data—
Mon 5 OctLiberec 17:49No data—
Fri 2 Oct— 18:05+3 min+7 min
Thu 1 Oct— 18:020 min+2 min
Wed 30 Sept— 18:030 min+4 min
Tue 29 Sept— 18:01−1 min+1 min
Fri 25 Sept— 18:030 min+2 min
Thu 24 Sept— 18:01−1 min+4 min
Wed 23 Sept— 18:02−1 min+1 min
Tue 22 Sept— 18:020 min+6 min