Os 6347 6347 Černousy – Liberec

View line Os 6347

Černousy 17:33 → Liberec 18:23 Daily 0 h 50 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Černousy17:33
  2. Višňová17:38
  3. Minkovice17:40
  4. Raspenava17:54
  5. Mníšek u Liberce18:10
  6. Krásná Studánka18:14
  7. Liberec18:23

Next service: tomorrow 17:33 from Černousy · Fri 6 Nov

Next departure 17:33 tomorrow · Černousy
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
90%
52/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 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

Worst days

  • Fri 4 Sept Max en route +14 min · last fix heading to — +11 min
  • Sun 6 Sept Max en route +8 min · last fix heading to — +5 min
  • Thu 13 Aug Max en route +6 min · last fix heading to — +4 min
  • Sat 19 Sept Max en route +5 min · last fix heading to — +3 min
  • Thu 20 Aug Max en route +6 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 14% · 8
  • On time 76% · 44
  • 3–10 min 9% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 75% T n=8
  • 75% F n=8
  • 89% S n=9
  • 89% S n=9

Stops and timetable

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

Last 90 days, 58 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
17:33on time on time
17:35≈ on time ≈ on time
17:38≈ on time ≈ on time
17:40≈ on time ≈ on time
17:47 / 17:48≈ on time ≈ +1 min
17:54 / 17:59≈ on time ≈ +1 min
18:06≈ on time ≈ +2 min
18:10≈ on time ≈ +2 min
18:14≈ on time ≈ +2 min
18:16≈ on time ≈ +2 min
18: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
Thu 5 NovLiberec 18:24No data—
Wed 4 NovLiberec 18:24No data—
Tue 3 NovLiberec 18:24No data—
Mon 2 NovLiberec 18:24No data—
Sun 1 NovLiberec 18:24No data—
Sat 31 OctLiberec 18:24No data—
Fri 30 OctLiberec 18:24No data—
Thu 29 OctLiberec 18:24No data—
Wed 28 OctLiberec 18:24No data—
Tue 27 OctLiberec 18:25No data—
Mon 26 OctLiberec 18:24No data—
Sun 25 OctLiberec 18:24No data—
Sat 24 OctLiberec 18:24No data—
Fri 23 OctLiberec 18:25No data—
Thu 22 OctLiberec 18:24No data—
Wed 21 OctLiberec 18:24No data—
Tue 20 OctLiberec 18:25No data—
Mon 19 OctLiberec 18:24No data—
Sun 18 OctLiberec 18:25No data—
Sat 17 OctLiberec 18:24No data—
Fri 16 OctLiberec 18:24No data—
Thu 15 OctLiberec 18:24No data—
Wed 14 OctLiberec 18:24No data—
Tue 13 OctLiberec 18:24No data—
Mon 12 OctLiberec 18:25No data—
Sun 11 OctLiberec 18:24No data—
Sat 10 OctLiberec 18:24No data—
Fri 9 OctLiberec 18:24No data—
Thu 8 OctLiberec 18:24No data—
Wed 7 OctLiberec 18:24No data—