Os 6339 6339 Černousy – Liberec

View line Os 6339

Černousy 11:38 → Liberec 12:23 Mon, Tue, Wed, Thu, Fri 0 h 45 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Černousy11:38
  2. Višňová11:43
  3. Minkovice11:45
  4. Raspenava11:59
  5. Mníšek u Liberce12:10
  6. Krásná Studánka12:14
  7. Liberec12:23

Next service: Monday 11:38 from Černousy · Mon 9 Nov

Next departure 11:38 Monday · Černousy
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 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

  • Wed 30 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 13% · 5
  • On time 85% · 34
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 88% 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, 40 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
11:38on time on time
11:40≈ on time ≈ on time
11:43≈ on time ≈ on time
11:45≈ on time ≈ on time
11:52 / 11:53≈ on time ≈ +1 min
11:59≈ on time ≈ +1 min
12:06≈ on time ≈ +1 min
12:10≈ on time ≈ +1 min
12:14≈ on time ≈ +1 min
12:16≈ on time ≈ +1 min
12: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
Fri 6 NovLiberec 12:24No data—
Thu 5 NovLiberec 12:24No data—
Wed 4 NovLiberec 12:24No data—
Tue 3 NovLiberec 12:24No data—
Mon 2 NovLiberec 12:24No data—
Fri 30 OctLiberec 12:24No data—
Thu 29 OctLiberec 12:24No data—
Tue 27 OctLiberec 12:24No data—
Mon 26 OctLiberec 12:24No data—
Fri 23 OctLiberec 12:24No data—
Thu 22 OctLiberec 12:24No data—
Wed 21 OctLiberec 12:24No data—
Tue 20 OctLiberec 12:24No data—
Mon 19 OctLiberec 12:24No data—
Fri 16 OctLiberec 12:24No data—
Thu 15 OctLiberec 12:24No data—
Wed 14 OctLiberec 12:24No data—
Tue 13 OctLiberec 12:24No data—
Mon 12 OctLiberec 12:24No data—
Fri 9 OctLiberec 12:24No data—
Thu 8 OctLiberec 12:24No data—
Wed 7 OctLiberec 12:24No data—
Tue 6 OctLiberec 12:24No data—
Mon 5 Oct— 12:38+1 min+3 min
Fri 2 Oct— 12:38+1 min+1 min
Thu 1 Oct— 12:37−1 min+2 min
Wed 30 Sept— 12:40+3 min+3 min
Tue 29 Sept— 12:370 min+2 min
Fri 25 Sept— 12:35−2 min—
Thu 24 Sept— 12:40+2 min+3 min