Os 5412 5412 Stará Paka – Liberec

View line Os 5412

Stará Paka 09:36 → Liberec 11:22 Daily 1 h 46 min · 20 stops ARRIVA vlaky s.r.o.

✓ Today’s run finished

Today, last fix heading to Liberec at 11:23 No data

  1. Stará Paka09:36
  2. Košťálov09:47
  3. Železný Brod10:03
  4. Turnov10:22
  5. Sedlejovice10:51
  6. Rádlo11:07
  7. Liberec11:22

Next service: tomorrow 09:36 from Stará Paka · Fri 13 Nov

Next departure 09:36 tomorrow · Stará Paka
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
69%
36/52 runs under 3 min
RT coverage: 52 full · 0 partial · 38 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+8min
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

  • Tue 8 Sept Max en route +18 min · last fix heading to — +17 min
  • Sat 5 Sept Max en route +18 min · last fix heading to — +15 min
  • Sun 27 Sept Max en route +15 min · last fix heading to — +13 min
  • Sat 3 Oct Max en route +11 min · last fix heading to — +8 min
  • Wed 30 Sept Max en route +10 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 10% · 5
  • On time 60% · 31
  • 3–10 min 25% · 13
  • 10–30 min 6% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 86% T n=7
  • 71% W n=7
  • 71% T n=7
  • 86% F n=7
  • 38% S n=8
  • 50% S n=8

Stops and timetable

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

Last 90 days, 52 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
09:36+1 min +7 min
09:40≈ +1 min ≈ +7 min
09:44≈ +1 min ≈ +7 min
09:47≈ +1 min ≈ +6 min
09:51≈ +1 min ≈ +6 min
09:55 / 09:56≈ +1 min ≈ +6 min
10:03 / 10:04≈ +1 min ≈ +6 min
10:08≈ +1 min ≈ +6 min
10:11 / 10:12≈ +1 min ≈ +6 min
10:17≈ +1 min ≈ +7 min
10:22 / 10:40≈ +1 min ≈ +7 min
10:45≈ +1 min ≈ +6 min
10:49≈ +1 min ≈ +6 min
10:51≈ +1 min ≈ +6 min
10:56 / 10:57≈ +1 min ≈ +6 min
11:02 / 11:03≈ +1 min ≈ +7 min
11:07≈ +1 min ≈ +7 min
11:10≈ +1 min ≈ +7 min
11:15≈ +1 min ≈ +8 min
11:22+1 min +8 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 12 NovLiberec 11:23No data—
Wed 11 NovLiberec 11:23No data—
Tue 10 NovLiberec 11:24No data—
Mon 9 NovLiberec 11:23No data—
Sun 8 NovLiberec 11:23No data—
Sat 7 NovLiberec 11:23No data—
Fri 6 NovLiberec 11:23No data—
Thu 5 NovLiberec 11:23No data—
Wed 4 NovLiberec 11:23No data—
Tue 3 NovLiberec 11:23No data—
Mon 2 NovLiberec 11:23No data—
Sun 1 NovLiberec 11:23No data—
Sat 31 OctLiberec 11:23No data—
Fri 30 OctLiberec 11:23No data—
Thu 29 OctLiberec 11:23No data—
Wed 28 OctLiberec 11:23No data—
Tue 27 OctLiberec 11:23No data—
Mon 26 OctLiberec 11:23No data—
Sun 25 OctLiberec 11:23No data—
Sat 24 OctLiberec 11:23No data—
Fri 23 OctLiberec 11:23No data—
Thu 22 OctLiberec 11:23No data—
Wed 21 OctLiberec 11:23No data—
Tue 20 OctLiberec 11:23No data—
Mon 19 OctLiberec 11:23No data—
Sun 18 OctLiberec 11:23No data—
Sat 17 OctLiberec 11:23No data—
Fri 16 OctLiberec 11:23No data—
Thu 15 OctLiberec 11:23No data—
Wed 14 OctLiberec 11:23No data—