Ł 99661 Skierniewice – Kutno

View line Ł

Skierniewice 08:38 → Kutno 09:30 Mon, Tue, Wed, Thu, Fri 0 h 52 min · 13 stops ŁKA

✓ Today’s run finished

Today it reached Kutno at 09:30 0 min

  1. Skierniewice08:38
  2. Sierakowice Skierniewickie08:44
  3. Bobrowniki08:51
  4. Niedźwiada Łowicka09:01
  5. Zosinów09:10
  6. Złotniki Kutnowskie09:21
  7. Kutno09:30

Next service: tomorrow 08:38 from Skierniewice · Wed 18 Nov

Next departure 08:38 tomorrow · 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
92%
36/39 runs under 3 min
RT coverage: 39 full · 0 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Tue 1 Sept Max en route +7 min · last fix heading to Sklęczki +7 min
  • Fri 18 Sept Max en route +3 min · last fix heading to Sklęczki +3 min
  • Fri 4 Sept Max en route +3 min · last fix heading to Sklęczki +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 36
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 89% T n=9
  • 100% W n=6
  • 100% T n=7
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
08:38on time +2 min
08:41 / 08:42≈ on time ≈ +2 min
08:44 / 08:45≈ on time ≈ +2 min
08:48≈ on time ≈ +2 min
08:51≈ on time ≈ +2 min
08:56 / 08:57≈ on time ≈ +2 min
09:01≈ on time ≈ +2 min
09:06≈ on time ≈ +2 min
09:10 / 09:11≈ on time ≈ +2 min
09:16≈ on time ≈ +2 min
09:21 / 09:22≈ on time ≈ +2 min
09:26≈ on time ≈ +2 min
09:30on 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 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
Tue 17 NovKutno 09:290 min—
Mon 16 NovKutno 09:32+1 min+1 min
Fri 13 NovKutno 09:290 min—
Thu 12 NovKutno 09:320 min—
Tue 10 NovKutno 09:290 min—
Mon 9 NovKutno 09:290 min—
Fri 6 NovKutno 09:290 min—
Thu 5 NovKutno 09:290 min—
Wed 4 NovKutno 09:32+1 min+1 min
Tue 3 NovKutno 09:290 min—
Mon 2 NovKutno 09:290 min—
Fri 30 OctKutno 09:310 min—
Thu 29 OctKutno 09:310 min—
Wed 28 OctKutno 09:32+1 min+1 min
Tue 27 OctKutno 09:32+1 min+1 min
Mon 26 OctKutno 09:310 min—
Fri 23 OctKutno 09:31No data—
Thu 22 OctKutno 09:32No data—
Wed 21 OctKutno 09:31No data—
Tue 20 OctKutno 09:31No data—
Mon 19 OctKutno 09:310 min—
Fri 16 OctKutno 09:320 min—
Thu 15 OctKutno 09:33+1 min+1 min
Wed 14 OctKutno 09:320 min—
Tue 13 OctKutno 09:310 min—
Mon 12 OctKutno 09:320 min+1 min
Fri 9 OctKutno 09:320 min—
Thu 8 OctKutno 09:320 min—
Wed 7 OctKutno 09:320 min—
Tue 6 OctKutno 09:320 min—