Os 2648 2648 Liberec – Tanvald

View line Os 2648

Liberec 21:35 → Tanvald 22:25 Daily 0 h 50 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 21:35 from Liberec · Thu 5 Nov

Next departure 21:35 today · Liberec
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
95%
55/58 runs under 3 min
RT coverage: 58 full · 0 partial · 31 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Tanvald, 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 +27 min · last fix heading to — +27 min
  • Sat 15 Aug Max en route +7 min · last fix heading to — +4 min
  • Thu 13 Aug Max en route +9 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 48% · 28
  • On time 47% · 27
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 88% T n=8
  • 88% F n=8
  • 89% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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
21:35on time +4 min
21:38≈ on time ≈ +4 min
21:41≈ on time ≈ +4 min
21:42≈ on time ≈ +4 min
21:45≈ on time ≈ +3 min
21:50≈ on time ≈ +3 min
21:55 / 21:56≈ on time ≈ +2 min
21:57≈ on time ≈ +2 min
21:59≈ on time ≈ +2 min
22:00≈ on time ≈ +2 min
22:02≈ on time ≈ +2 min
22:06≈ 1 min early ≈ +1 min
22:11 / 22:12≈ 1 min early ≈ +1 min
22:13≈ 1 min early ≈ +1 min
22:14≈ 1 min early ≈ +1 min
22:17≈ 1 min early ≈ +1 min
22:20≈ 1 min early ≈ +1 min
22:251 min early on time

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 NovTanvald 22:24No data—
Tue 3 NovTanvald 22:24No data—
Mon 2 NovTanvald 22:24No data—
Sun 1 NovTanvald 22:24No data—
Sat 31 OctTanvald 22:26No data—
Fri 30 OctTanvald 22:26No data—
Thu 29 OctTanvald 22:26No data—
Wed 28 OctTanvald 22:26No data—
Tue 27 OctTanvald 22:27No data—
Mon 26 OctTanvald 22:26No data—
Sun 25 OctTanvald 22:26No data—
Sat 24 OctTanvald 22:26No data—
Fri 23 OctTanvald 22:26No data—
Thu 22 OctTanvald 22:26No data—
Wed 21 OctTanvald 22:26No data—
Tue 20 OctTanvald 22:26No data—
Mon 19 OctTanvald 22:27No data—
Sun 18 OctTanvald 22:26No data—
Sat 17 OctTanvald 22:26No data—
Fri 16 OctTanvald 22:26No data—
Thu 15 OctTanvald 22:26No data—
Wed 14 OctTanvald 22:26No data—
Tue 13 OctTanvald 22:26No data—
Mon 12 OctTanvald 22:26No data—
Sun 11 OctTanvald 22:26No data—
Sat 10 OctTanvald 22:26No data—
Fri 9 OctTanvald 22:26No data—
Thu 8 OctTanvald 22:27No data—
Wed 7 OctTanvald 22:26No data—
Tue 6 OctTanvald 22:26No data—