Os 2625 2625 Tanvald – Liberec

View line Os 2625

Tanvald 14:59 → Liberec 15: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: Friday 13 November No data

Next service: today 14:59 from Tanvald · Mon 16 Nov

Next departure 14:59 today · Tanvald
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
82%
27/33 runs under 3 min
RT coverage: 33 full · 0 partial · 28 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 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

  • Wed 9 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 8 Sept Max en route +5 min · last fix heading to — +4 min
  • Thu 20 Aug Max en route +5 min · last fix heading to — +4 min
  • Wed 16 Sept Max en route +5 min · last fix heading to — +3 min
  • Mon 7 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 27
  • 3–10 min 18% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 71% W n=7
  • 71% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

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