Os 6355 6355 Frýdlant v Č. – Liberec

View line Os 6355

Frýdlant v Č. 06:53 → Liberec 07:23 Sat, Sun 0 h 30 min · 7 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Liberec at 07:24 No data

  1. Frýdlant v Č.06:53
  2. Raspenava06:59
  3. Oldřichov v Hájích07:06
  4. Mníšek u Liberce07:10
  5. Krásná Studánka07:14
  6. Stráž nad Nisou07:16
  7. Liberec07:23

Next service: Saturday 06:53 from Frýdlant v Č. · Sat 14 Nov

Next departure 06:53 Saturday · Frýdlant v Č.
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
−2min
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

Distribution · 90 days

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

  • Early 59% · 10
  • On time 41% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 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, 17 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
06:53on time on time
06:59≈ on time ≈ on time
07:06≈ 1 min early ≈ on time
07:10≈ 1 min early ≈ on time
07:14≈ 1 min early ≈ on time
07:16≈ 2 min early ≈ on time
07:232 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
Sun 8 NovLiberec 07:24No data—
Sat 7 NovLiberec 07:24No data—
Sun 1 NovLiberec 07:24No data—
Sat 31 OctLiberec 07:24No data—
Wed 28 OctLiberec 07:24No data—
Sun 25 OctLiberec 07:24No data—
Sat 24 OctLiberec 07:24No data—
Sun 18 OctLiberec 07:25No data—
Sat 17 OctLiberec 07:24No data—
Sun 11 OctLiberec 07:24No data—
Sat 10 OctLiberec 07:24No data—
Sun 4 Oct— 07:36−2 min—
Sat 3 Oct— 07:37−1 min—
Mon 28 Sept— 07:34−4 min—
Sun 27 Sept— 07:36−2 min+1 min
Sat 26 Sept— 07:380 min—
Sun 20 Sept— 07:35−2 min—
Sat 19 Sept— 07:36−2 min—
Sun 13 Sept— 07:36−1 min—
Sat 12 Sept— 07:36−2 min—
Sun 6 Sept— 07:35−2 min—
Sat 5 Sept— 07:36−1 min+2 min
Sun 30 Aug— 07:35−2 min—
Sat 29 Aug— 07:37−1 min—
Sun 23 Aug— 07:34−3 min—
Sat 22 Aug— 07:36−1 min+1 min
Sun 16 Aug— 07:38+1 min+1 min
Sat 15 Aug— 07:35−2 min—