Ł 99667 Skierniewice – Kutno

View line Ł

Skierniewice 13:34 → Kutno 14:27 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 13 stops ŁKA

✓ Today’s run finished

Today it reached Kutno at 14:27 0 min

  1. Skierniewice13:34
  2. Sierakowice Skierniewickie13:41
  3. Bobrowniki13:47
  4. Niedźwiada Łowicka13:58
  5. Zosinów14:07
  6. Złotniki Kutnowskie14:18
  7. Kutno14:27

Next service: tomorrow 13:34 from Skierniewice · Fri 20 Nov

Next departure 13:34 tomorrow · Skierniewice
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 3 no data
On-time · 90 days
73%
29/40 runs under 3 min
RT coverage: 40 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +4 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 8 Sept Max en route +7 min · last fix heading to Sklęczki +7 min
  • Mon 16 Nov Max en route +8 min · last fix heading to Kutno +6 min
  • Fri 25 Sept Max en route +6 min · last fix heading to Sklęczki +6 min
  • Thu 24 Sept Max en route +6 min · last fix heading to Sklęczki +6 min
  • Wed 23 Sept Max en route +7 min · last fix heading to Sklęczki +6 min

Distribution · 90 days

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

  • Early 10% · 4
  • On time 63% · 25
  • 3–10 min 28% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 56% T n=9
  • 78% W n=9
  • 86% T n=7
  • 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, 40 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
13:34on time +5 min
13:38≈ on time ≈ +5 min
13:41≈ on time ≈ +5 min
13:44≈ on time ≈ +5 min
13:47 / 13:48≈ on time ≈ +5 min
13:53 / 13:54≈ on time ≈ +5 min
13:58 / 13:59≈ on time ≈ +6 min
14:03≈ on time ≈ +6 min
14:07 / 14:08≈ on time ≈ +6 min
14:13≈ on time ≈ +6 min
14:18 / 14:19≈ on time ≈ +6 min
14:23≈ on time ≈ +6 min
14:27on time +6 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
Thu 19 NovKutno 14:280 min—
Wed 18 NovKutno 14:280 min—
Tue 17 NovKutno 14:32+4 min+4 min
Mon 16 NovKutno 14:34+6 min+8 min
Fri 13 NovKutno 14:290 min—
Thu 12 NovKutno 14:280 min—
Tue 10 NovKutno 14:280 min—
Mon 9 NovKutno 14:290 min—
Fri 6 NovKutno 14:280 min—
Thu 5 NovKutno 14:280 min—
Wed 4 NovKutno 14:280 min—
Tue 3 NovKutno 14:30+1 min+1 min
Mon 2 NovKutno 14:280 min+2 min
Fri 30 OctKutno 14:280 min—
Thu 29 OctKutno 14:280 min—
Wed 28 OctKutno 14:32+4 min+4 min
Tue 27 OctKutno 14:26−2 min—
Mon 26 OctKutno 14:290 min—
Fri 23 OctKutno 14:28No data—
Thu 22 OctKutno 14:28No data—
Wed 21 OctKutno 14:29No data—
Tue 20 OctKutno 14:28No data—
Mon 19 OctKutno 14:29No data—
Fri 16 OctKutno 14:280 min—
Thu 15 OctKutno 14:280 min—
Wed 14 OctKutno 14:280 min—
Tue 13 OctKutno 14:280 min—
Mon 12 OctKutno 14:280 min—
Fri 9 OctKutno 14:280 min—
Thu 8 OctKutno 14:280 min—