Ł 99665 Skierniewice – Kutno

View line Ł

Skierniewice 12:28 → Kutno 13:22 Mon, Tue, Wed, Thu, Fri 0 h 54 min · 13 stops ŁKA

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 12:28 from Skierniewice · Tue 17 Nov

Next departure 12:28 today · Skierniewice
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 6 no data
On-time · 90 days
93%
25/27 runs under 3 min
RT coverage: 27 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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 2 Oct Max en route +8 min · last fix heading to Złotniki Kutnowskie +8 min
  • Fri 11 Sept Max en route +8 min · last fix heading to Złotniki Kutnowskie +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 25
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=4
  • 100% T n=5
  • 71% 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, 27 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
12:28on time on time
12:31 / 12:32≈ on time ≈ on time
12:34 / 12:35≈ on time ≈ on time
12:38≈ on time ≈ on time
12:41≈ on time ≈ on time
12:47 / 12:49≈ on time ≈ on time
12:53≈ on time ≈ on time
12:58≈ on time ≈ on time
13:02 / 13:03≈ on time ≈ on time
13:08≈ on time ≈ on time
13:13 / 13:14≈ on time ≈ on time
13:18≈ on time ≈ on time
13:22on time on time

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
Mon 16 NovKutno 13:240 min—
Fri 13 NovKutno 13:230 min—
Thu 12 NovKutno 13:230 min—
Tue 10 NovKutno 13:240 min—
Mon 9 NovKutno 13:240 min—
Fri 6 NovKutno 13:230 min—
Thu 5 NovKutno 13:230 min—
Wed 4 NovKutno 13:230 min—
Tue 3 NovKutno 13:230 min—
Mon 2 NovKutno 13:23No data—
Fri 30 OctKutno 13:230 min—
Thu 29 OctKutno 13:230 min—
Wed 28 OctKutno 13:230 min—
Tue 27 OctKutno 13:230 min—
Mon 26 OctKutno 13:230 min+1 min
Fri 23 OctKutno 13:23No data—
Thu 22 OctKutno 13:23No data—
Wed 21 OctKutno 13:23No data—
Tue 20 OctKutno 13:24No data—
Mon 19 OctKutno 13:23No data—
Fri 16 OctKutno 13:230 min—
Thu 15 OctKutno 13:230 min—
Wed 14 OctKutno 13:240 min—
Tue 13 OctKutno 13:230 min—
Mon 12 OctKutno 13:230 min—
Fri 9 OctKutno 13:230 min—
Thu 8 OctKutno 13:230 min—
Wed 7 OctKutno 13:230 min—
Tue 6 OctKutno 13:230 min—
Mon 5 OctKutno 13:230 min—