Os 6309 6309 Černousy – Liberec

View line Os 6309

Černousy 05:38 → Liberec 06:23 Sat, Sun 0 h 45 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Černousy05:38
  2. Višňová05:43
  3. Minkovice05:45
  4. Raspenava05:59
  5. Mníšek u Liberce06:10
  6. Krásná Studánka06:14
  7. Liberec06:23

Next service: Saturday 05:38 from Černousy · Sat 14 Nov

Next departure 05:38 Saturday · Černousy
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
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
0min
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

  • Sat 12 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 12% · 2
  • On time 82% · 14
  • 3–10 min 6% · 1
  • 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
  • 88% S n=8
  • 100% S n=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
05:38on time on time
05:40≈ on time ≈ on time
05:43≈ on time ≈ on time
05:45≈ on time ≈ on time
05:52 / 05:53≈ on time ≈ on time
05:59≈ on time ≈ +1 min
06:06≈ on time ≈ +1 min
06:10≈ on time ≈ +1 min
06:14≈ on time ≈ +1 min
06:16≈ on time ≈ +1 min
06:23on time +1 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
Sun 8 NovLiberec 06:24No data—
Sat 7 NovLiberec 06:24No data—
Sun 1 NovLiberec 06:24No data—
Sat 31 OctLiberec 06:24No data—
Wed 28 OctLiberec 06:24No data—
Sun 25 OctLiberec 06:24No data—
Sat 24 OctLiberec 06:24No data—
Sun 18 OctLiberec 06:24No data—
Sat 17 OctLiberec 06:24No data—
Sun 11 OctLiberec 06:24No data—
Sat 10 OctLiberec 06:24No data—
Sun 4 Oct— 06:380 min+2 min
Sat 3 Oct— 06:36−1 min—
Mon 28 Sept— 06:37−1 min—
Sun 27 Sept— 06:380 min—
Sat 26 Sept— 06:39+2 min+2 min
Sun 20 Sept— 06:370 min+1 min
Sat 19 Sept— 06:37−1 min—
Sun 13 Sept— 06:370 min+2 min
Sat 12 Sept— 06:41+3 min+3 min
Sun 6 Sept— 06:35−2 min—
Sat 5 Sept— 06:37−1 min—
Sun 30 Aug— 06:36−1 min—
Sat 29 Aug— 06:35−2 min—
Sun 23 Aug— 06:370 min+1 min
Sat 22 Aug— 06:36−1 min—
Sun 16 Aug— 06:38+1 min+2 min
Sat 15 Aug— 06:370 min+1 min