Ł 99663 Skierniewice – Kutno

View line Ł

Skierniewice 10:24 → Kutno 11:18 Mon, Tue, Wed, Thu, Fri 0 h 54 min · 13 stops ŁKA

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 10:24 from Skierniewice · Mon 9 Nov

Next departure 10:24 Monday · Skierniewice
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 4 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 14 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Kutno, 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 +5 min · last fix heading to Sklęczki +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 35
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=8
  • 100% T n=8
  • 86% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
10:24on time +1 min
10:28≈ on time ≈ +1 min
10:32≈ on time ≈ +1 min
10:35 / 10:36≈ on time ≈ +1 min
10:39≈ on time ≈ +1 min
10:44 / 10:46≈ on time ≈ +1 min
10:50 / 10:51≈ on time ≈ +1 min
10:55≈ on time ≈ +1 min
10:59 / 11:00≈ on time ≈ +1 min
11:04 / 11:05≈ on time ≈ +1 min
11:10≈ on time ≈ +1 min
11:14 / 11:15≈ on time ≈ +1 min
11:18on 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 1 August 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 NovKutno 11:190 min—
Thu 5 NovKutno 11:190 min—
Wed 4 NovKutno 11:190 min—
Tue 3 NovKutno 11:190 min—
Mon 2 NovKutno 11:190 min—
Fri 30 OctKutno 11:190 min—
Thu 29 OctKutno 11:190 min—
Wed 28 OctKutno 11:190 min—
Tue 27 OctKutno 11:190 min—
Mon 26 OctKutno 11:190 min—
Fri 23 OctKutno 11:19No data—
Thu 22 OctKutno 11:19No data—
Wed 21 OctKutno 11:19No data—
Tue 20 OctKutno 11:19No data—
Mon 19 OctKutno 11:190 min—
Fri 16 OctKutno 11:190 min—
Thu 15 OctKutno 11:190 min—
Wed 14 OctKutno 11:200 min—
Tue 13 OctKutno 11:190 min—
Mon 12 OctKutno 11:190 min+1 min
Fri 9 OctKutno 11:200 min—
Thu 8 OctKutno 11:190 min—
Wed 7 OctKutno 11:190 min—
Tue 6 OctKutno 11:190 min—
Mon 5 OctKutno 11:190 min—
Fri 2 OctKutno 11:17No data—
Thu 1 OctKutno 11:17+1 min+1 min
Wed 30 SeptKutno 11:17No data—
Tue 29 SeptKutno 11:18No data—
Mon 28 SeptKutno 11:18No data—