Os 6303 6303 Černousy – Liberec

View line Os 6303

Černousy 04:26 → Liberec 05:23 Mon, Tue, Wed, Thu, Fri 0 h 57 min · 11 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 04:26 from Černousy · Mon 9 Nov

Full trip card
Next departure 04:26 tomorrow · Černousy
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
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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

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

  • Early 10% · 4
  • On time 90% · 35
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
Černousy
04:26on time on time
Filipovka
04:28≈ on time ≈ on time
Višňová
04:31≈ on time ≈ on time
Minkovice
04:33≈ on time ≈ on time
Frýdlant v Č.
04:40 / 04:48≈ on time ≈ on time
Raspenava
04:54 / 04:59≈ on time ≈ +1 min
Oldřichov v Hájích
05:06≈ on time ≈ +1 min
Mníšek u Liberce
05:10≈ on time ≈ +2 min
Krásná Studánka
05:14≈ on time ≈ +2 min
Stráž nad Nisou
05:16≈ on time ≈ +2 min
Liberec
05:23on time +2 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 6 NovLiberec 05:24No data—
Thu 5 NovLiberec 05:24No data—
Wed 4 NovLiberec 05:24No data—
Tue 3 NovLiberec 05:25No data—
Mon 2 NovLiberec 05:24No data—
Fri 30 OctLiberec 05:24No data—
Thu 29 OctLiberec 05:24No data—
Tue 27 OctLiberec 05:24No data—
Mon 26 OctLiberec 05:24No data—
Fri 23 OctLiberec 05:24No data—
Thu 22 OctLiberec 05:24No data—
Wed 21 OctLiberec 05:24No data—
Tue 20 OctLiberec 05:24No data—
Mon 19 OctLiberec 05:24No data—
Fri 16 OctLiberec 05:24No data—
Thu 15 OctLiberec 05:24No data—
Wed 14 OctLiberec 05:24No data—
Tue 13 OctLiberec 05:24No data—
Mon 12 OctLiberec 05:24No data—
Fri 9 OctLiberec 05:24No data—
Thu 8 OctLiberec 05:24No data—
Wed 7 OctLiberec 05:24No data—
Tue 6 OctLiberec 05:24No data—
Mon 5 Oct— 05:380 min+2 min
Fri 2 Oct— 05:36−1 min—
Thu 1 Oct— 05:370 min—
Wed 30 Sept— 05:370 min+1 min
Tue 29 Sept— 05:370 min+1 min
Fri 25 Sept— 05:40+2 min+2 min
Thu 24 Sept— 05:39+2 min+2 min