Sp 1441 1441 Lipová Lázně – Krnov

View line Sp 1441

Lipová Lázně 05:17 → Krnov 06:55 Daily 1 h 38 min · 15 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Krnov at 06:54 No data

  1. Lipová Lázně05:17
  2. Jeseník05:23
  3. Písečná05:39
  4. Mikulovice05:49
  5. Jindřichov ve Slezsku06:27
  6. Linhartovy06:47
  7. Krnov06:55

Next service: tomorrow 05:17 from Lipová Lázně · Sun 15 Nov

Next departure 05:17 tomorrow · Lipová Lázně
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
58%
15/26 runs under 3 min
RT coverage: 26 full · 0 partial · 40 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Krnov, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 17 Aug Max en route +10 min · last fix heading to — +10 min
  • Thu 27 Aug Max en route +6 min · last fix heading to — +6 min
  • Sun 30 Aug Max en route +4 min · last fix heading to — +4 min
  • Sat 22 Aug Max en route +4 min · last fix heading to — +4 min
  • Fri 21 Aug Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 58% · 15
  • 3–10 min 38% · 10
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 50% T n=2
  • 50% W n=2
  • 50% T n=2
  • 50% F n=2
  • 43% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 26 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:17on time on time
05:20≈ on time ≈ on time
05:23 / 05:28≈ on time ≈ on time
05:32≈ on time ≈ +1 min
05:34≈ on time ≈ +1 min
05:39 / 05:40≈ on time ≈ +1 min
05:43≈ on time ≈ +1 min
05:49 / 05:50≈ +1 min ≈ +1 min
06:03 / 06:09≈ +1 min ≈ +2 min
06:27 / 06:28≈ +1 min ≈ +3 min
06:36≈ +1 min ≈ +3 min
06:41≈ +1 min ≈ +3 min
06:47≈ +1 min ≈ +4 min
06:49≈ +1 min ≈ +4 min
06:55+2 min +4 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
Sat 14 NovKrnov 06:54No data—
Fri 13 NovKrnov 06:54No data—
Thu 12 NovKrnov 06:54No data—
Wed 11 NovKrnov 06:54No data—
Tue 10 NovKrnov 06:55No data—
Mon 9 NovKrnov 06:54No data—
Sun 8 NovKrnov 06:54No data—
Sat 7 NovKrnov 06:54No data—
Fri 6 NovKrnov 06:54No data—
Thu 5 NovKrnov 06:54No data—
Wed 4 NovKrnov 06:54No data—
Tue 3 NovKrnov 06:54No data—
Mon 2 NovKrnov 06:54No data—
Sun 1 NovKrnov 06:56No data—
Sat 31 OctKrnov 06:56No data—
Fri 30 OctKrnov 06:56No data—
Thu 29 OctKrnov 06:56No data—
Wed 28 OctKrnov 06:56No data—
Tue 27 OctKrnov 06:56No data—
Mon 26 OctKrnov 06:56No data—
Sun 25 OctKrnov 06:56No data—
Sat 24 OctKrnov 06:56No data—
Fri 23 OctKrnov 06:56No data—
Thu 22 OctKrnov 06:56No data—
Wed 21 OctKrnov 06:56No data—
Tue 20 OctKrnov 06:56No data—
Mon 19 OctKrnov 06:56No data—
Sun 18 OctKrnov 06:56No data—
Sat 17 OctKrnov 06:56No data—
Fri 16 OctKrnov 06:56No data—