Os 6329 6329 Frýdlant v Č. – Liberec

View line Os 6329

Frýdlant v Č. 21:54 → Liberec 22:25 Daily 0 h 31 min · 7 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 21:54 from Frýdlant v Č. · Mon 9 Nov

Next departure 21:54 today · Frýdlant v Č.
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
98%
53/54 runs under 3 min
RT coverage: 54 full · 0 partial · 35 no data
Typical delay
−2min
Median at arrival, 90 days
P90
0min
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 +6 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 65% · 35
  • On time 33% · 18
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 55 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:54on time on time
22:00 / 22:01≈ on time ≈ on time
22:08≈ 1 min early ≈ on time
22:12≈ 1 min early ≈ on time
22:16≈ 1 min early ≈ on time
22:18≈ 2 min early ≈ on time
22:252 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
Sun 8 NovLiberec 22:24No data—
Sat 7 NovLiberec 22:24No data—
Fri 6 NovLiberec 22:24No data—
Thu 5 NovLiberec 22:24No data—
Wed 4 NovLiberec 22:24No data—
Tue 3 NovLiberec 22:24No data—
Mon 2 NovLiberec 22:24No data—
Sun 1 NovLiberec 22:24No data—
Sat 31 OctLiberec 22:26No data—
Fri 30 OctLiberec 22:26No data—
Thu 29 OctLiberec 22:26No data—
Wed 28 OctLiberec 22:26No data—
Tue 27 OctLiberec 22:27No data—
Mon 26 OctLiberec 22:26No data—
Sun 25 OctLiberec 22:26No data—
Sat 24 OctLiberec 22:26No data—
Fri 23 OctLiberec 22:26No data—
Thu 22 OctLiberec 22:26No data—
Wed 21 OctLiberec 22:26No data—
Tue 20 OctLiberec 22:26No data—
Mon 19 OctLiberec 22:27No data—
Sun 18 OctLiberec 22:26No data—
Sat 17 OctLiberec 22:26No data—
Fri 16 OctLiberec 22:26No data—
Thu 15 OctLiberec 22:26No data—
Wed 14 OctLiberec 22:26No data—
Tue 13 OctLiberec 22:26No data—
Mon 12 OctLiberec 22:26No data—
Sun 11 OctLiberec 22:26No data—
Sat 10 OctLiberec 22:26No data—