Sp 1290 1290 Horka u Staré Paky – Liberec

View line Sp 1290

Horka u Staré Paky 05:12 → Liberec 06:52 Mon, Tue, Wed, Thu, Fri 1 h 40 min · 22 stops ARRIVA vlaky s.r.o.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 05:12 from Horka u Staré Paky · Mon 9 Nov

Next departure 05:12 tomorrow · Horka u Staré Paky
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
64%
25/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+13min
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 1 Sept Max en route +31 min · last fix heading to — +31 min
  • Wed 12 Aug Max en route +23 min · last fix heading to — +23 min
  • Tue 29 Sept Max en route +19 min · last fix heading to — +18 min
  • Wed 9 Sept Max en route +14 min · last fix heading to — +14 min
  • Fri 11 Sept Max en route +13 min · last fix heading to — +13 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 62% · 24
  • 3–10 min 21% · 8
  • 10–30 min 13% · 5
  • 30+ min 3% · 1

On-time by weekday

  • 57% M n=7
  • 75% T n=8
  • 75% W n=8
  • 63% T n=8
  • 50% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (22 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
05:12on time on time
05:15≈ on time ≈ +1 min
05:21 / 05:27≈ on time ≈ +1 min
05:31≈ on time ≈ +3 min
05:35≈ on time ≈ +3 min
05:38≈ on time ≈ +3 min
05:42≈ on time ≈ +4 min
05:46 / 05:47≈ on time ≈ +4 min
05:54 / 05:55≈ on time ≈ +6 min
05:59≈ on time ≈ +6 min
06:01 / 06:02≈ on time ≈ +6 min
06:07≈ +1 min ≈ +7 min
06:10 / 06:14≈ +1 min ≈ +8 min
06:18≈ +1 min ≈ +9 min
06:21 / 06:22≈ +1 min ≈ +9 min
06:24≈ +1 min ≈ +10 min
06:28≈ +1 min ≈ +10 min
06:34 / 06:35≈ +1 min ≈ +11 min
06:39≈ +1 min ≈ +11 min
06:41 / 06:42≈ +1 min ≈ +12 min
06:47≈ +1 min ≈ +13 min
06:52+1 min +13 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 06:53No data—
Thu 5 NovLiberec 06:53No data—
Wed 4 NovLiberec 06:53No data—
Tue 3 NovLiberec 06:53No data—
Mon 2 NovLiberec 06:53No data—
Fri 30 OctLiberec 06:53No data—
Thu 29 OctLiberec 06:53No data—
Tue 27 OctLiberec 06:53No data—
Mon 26 OctLiberec 06:53No data—
Fri 23 OctLiberec 06:53No data—
Thu 22 OctLiberec 06:53No data—
Wed 21 OctLiberec 06:53No data—
Tue 20 OctLiberec 06:53No data—
Mon 19 OctLiberec 06:53No data—
Fri 16 OctLiberec 06:53No data—
Thu 15 OctLiberec 06:53No data—
Wed 14 OctLiberec 06:53No data—
Tue 13 OctLiberec 06:53No data—
Mon 12 OctLiberec 06:53No data—
Fri 9 OctLiberec 06:53No data—
Thu 8 OctLiberec 06:53No data—
Wed 7 OctLiberec 06:53No data—
Tue 6 OctLiberec 06:53No data—
Mon 5 Oct— 07:16+9 min+10 min
Fri 2 Oct— 07:06−1 min+2 min
Thu 1 Oct— 07:06−1 min—
Wed 30 Sept— 07:070 min+1 min
Tue 29 Sept— 07:25+18 min+19 min
Fri 25 Sept— 07:12+5 min+6 min
Thu 24 Sept— 07:08+2 min+3 min