Os 6325 6325 Frýdlant v Č. – Liberec

View line Os 6325

Frýdlant v Č. 18:53 → Liberec 19:25 Mon, Tue, Wed, Thu, Fri 0 h 32 min · 7 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 20 November No data

Next service: Monday 18:53 from Frýdlant v Č. · Mon 23 Nov

Next departure 18:53 Monday · Frýdlant v Č.
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
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 33 no data
Typical delay
−3min
Median at arrival, 90 days
P90
−1min
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 4 Sept Max en route +8 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 86% · 25
  • On time 10% · 3
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
18:53on time on time
18:58 / 18:59≈ on time ≈ on time
19:06≈ 1 min early ≈ on time
19:10≈ 2 min early ≈ 1 min early
19:14≈ 2 min early ≈ 1 min early
19:16≈ 2 min early ≈ 1 min early
19:253 min early 1 min early

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 20 NovLiberec 19:24No data—
Thu 19 NovLiberec 19:24No data—
Wed 18 NovLiberec 19:24No data—
Mon 16 NovLiberec 19:24No data—
Fri 13 NovLiberec 19:24No data—
Thu 12 NovLiberec 19:24No data—
Wed 11 NovLiberec 19:24No data—
Tue 10 NovLiberec 19:24No data—
Mon 9 NovLiberec 19:24No data—
Fri 6 NovLiberec 19:24No data—
Thu 5 NovLiberec 19:24No data—
Wed 4 NovLiberec 19:24No data—
Tue 3 NovLiberec 19:24No data—
Mon 2 NovLiberec 19:24No data—
Fri 30 OctLiberec 19:26No data—
Thu 29 OctLiberec 19:26No data—
Tue 27 OctLiberec 19:27No data—
Mon 26 OctLiberec 19:26No data—
Fri 23 OctLiberec 19:26No data—
Thu 22 OctLiberec 19:26No data—
Wed 21 OctLiberec 19:26No data—
Tue 20 OctLiberec 19:26No data—
Mon 19 OctLiberec 19:26No data—
Fri 16 OctLiberec 19:26No data—
Thu 15 OctLiberec 19:26No data—
Wed 14 OctLiberec 19:26No data—
Tue 13 OctLiberec 19:26No data—
Mon 12 OctLiberec 19:27No data—
Fri 9 OctLiberec 19:26No data—
Thu 8 OctLiberec 19:26No data—