Ł 97832 Łódź Widzew – Kutno

View line Ł

Łódź Widzew 21:02 → Kutno 22:46 Mon, Tue, Wed, Thu, Fri 1 h 44 min · 24 stops ŁKA

It has not run yet today

Last recorded run: Wednesday 18 November +6 min

Next service: today 21:02 from Łódź Widzew · Thu 19 Nov

Next departure 21:02 today · Łódź Widzew
On-time · 30 days
53%
9/17 runs under 3 min
RT coverage: 17 full · 0 partial · 3 no data
On-time · 90 days
36%
16/44 runs under 3 min
RT coverage: 44 full · 0 partial · 13 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +2 min
P90
+17min
9 in 10 runs arrive with less than this
30 days: +20 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 13 Nov Max en route +34 min · last fix heading to Kutno +34 min
  • Thu 12 Nov Max en route +34 min · last fix heading to Kutno +34 min
  • Thu 17 Sept Max en route +23 min · last fix heading to Gawrony +23 min
  • Fri 4 Sept Max en route +17 min · last fix heading to Witonia +17 min
  • Thu 3 Sept Max en route +17 min · last fix heading to Witonia +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 36% · 16
  • 3–10 min 39% · 17
  • 10–30 min 20% · 9
  • 30+ min 5% · 2

On-time by weekday

  • 38% M n=8
  • 44% T n=9
  • 44% W n=9
  • 11% T n=9
  • 44% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 44 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
21:02+3 min +16 min
21:08≈ +3 min ≈ +16 min
21:11 / 21:12≈ +3 min ≈ +16 min
21:15≈ +3 min ≈ +16 min
21:17≈ +3 min ≈ +16 min
21:22 / 21:23≈ +3 min ≈ +16 min
21:26≈ +3 min ≈ +16 min
21:30 / 21:38≈ +4 min ≈ +16 min
21:42 / 21:43≈ +4 min ≈ +16 min
21:45 / 21:46≈ +4 min ≈ +16 min
21:49 / 21:50≈ +4 min ≈ +16 min
21:52≈ +4 min ≈ +16 min
21:55≈ +4 min ≈ +16 min
21:58≈ +4 min ≈ +16 min
22:00≈ +4 min ≈ +16 min
22:02≈ +4 min ≈ +16 min
22:07≈ +4 min ≈ +16 min
22:10≈ +4 min ≈ +16 min
22:12≈ +4 min ≈ +16 min
22:17≈ +4 min ≈ +16 min
22:20≈ +4 min ≈ +16 min
22:28≈ +4 min ≈ +16 min
22:35≈ +4 min ≈ +16 min
22:46+4 min +17 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
Wed 18 NovKutno 22:54+6 min+6 min
Tue 17 NovKutno 22:45−1 min—
Mon 16 NovKutno 22:480 min—
Fri 13 NovKutno 23:22+34 min+34 min
Thu 12 NovKutno 23:22+34 min+34 min
Tue 10 NovKutno 22:480 min—
Mon 9 NovKutno 22:49+1 min+1 min
Fri 6 NovKutno 22:49+2 min+2 min
Thu 5 NovKutno 22:58+10 min+10 min
Wed 4 NovKutno 22:49+1 min+1 min
Tue 3 NovKutno 22:49+1 min+1 min
Mon 2 NovKutno 22:49+1 min+1 min
Fri 30 OctKutno 22:54+6 min+6 min
Thu 29 OctKutno 22:52+4 min+4 min
Wed 28 OctKutno 22:50+2 min+2 min
Tue 27 OctKutno 22:55+7 min+7 min
Mon 26 OctKutno 22:55+7 min+7 min
Fri 23 OctKutno 22:42No data—
Thu 22 OctKutno 22:41No data—
Wed 21 OctKutno 22:41No data—
Tue 20 OctKutno 22:41No data—
Mon 19 OctKutno 22:41No data—
Fri 16 OctKutno 22:410 min—
Thu 15 OctKutno 22:46+4 min+4 min
Wed 14 OctKutno 22:410 min—
Tue 13 OctKutno 22:44+3 min+3 min
Mon 12 OctKutno 22:44+3 min+3 min
Fri 9 OctKutno 22:410 min—
Thu 8 OctKutno 22:57+16 min+16 min
Wed 7 OctKutno 22:57+16 min+16 min