Ł 97822 Łódź Widzew – Kutno

View line Ł

Łódź Widzew 15:10 → Kutno 16:53 Mon, Tue, Wed, Thu, Fri 1 h 43 min · 22 stops ŁKA

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 15:10 from Łódź Widzew · Thu 19 Nov

Next departure 15:10 today · Łódź Widzew
On-time · 30 days
71%
17/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
47%
27/58 runs under 3 min
RT coverage: 58 full · 0 partial · 23 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: 0 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +11 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 10 Nov Max en route +39 min · last fix heading to Kutno +39 min
  • Mon 9 Nov Max en route +39 min · last fix heading to Kutno +39 min
  • Fri 18 Sept Max en route +24 min · last fix heading to Gawrony +24 min
  • Mon 31 Aug Max en route +20 min · last fix heading to Gawrony +18 min
  • Thu 15 Oct Max en route +15 min · last fix heading to Kutno +15 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 47% · 27
  • 3–10 min 24% · 14
  • 10–30 min 26% · 15
  • 30+ min 3% · 2

On-time by weekday

  • 44% M n=9
  • 38% T n=8
  • 56% W n=9
  • 22% T n=9
  • 44% F n=9
  • 71% S n=7
  • 57% S n=7

Stops and timetable

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

Last 90 days, 58 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
15:10+2 min +13 min
15:13 / 15:14≈ +2 min ≈ +13 min
15:16≈ +2 min ≈ +13 min
15:19 / 15:21≈ +3 min ≈ +13 min
15:24 / 15:25≈ +3 min ≈ +13 min
15:29 / 15:32≈ +3 min ≈ +13 min
15:36 / 15:37≈ +3 min ≈ +13 min
15:40 / 15:41≈ +3 min ≈ +13 min
15:44 / 15:47≈ +3 min ≈ +13 min
15:49 / 15:50≈ +3 min ≈ +14 min
15:52≈ +3 min ≈ +14 min
15:55≈ +3 min ≈ +14 min
15:57≈ +3 min ≈ +14 min
16:00≈ +3 min ≈ +14 min
16:04 / 16:09≈ +4 min ≈ +14 min
16:12 / 16:13≈ +4 min ≈ +14 min
16:14 / 16:15≈ +4 min ≈ +14 min
16:19≈ +4 min ≈ +14 min
16:22 / 16:28≈ +4 min ≈ +14 min
16:35 / 16:36≈ +4 min ≈ +14 min
16:42≈ +4 min ≈ +13 min
16:53+4 min +13 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 16:540 min—
Tue 17 NovKutno 16:540 min—
Mon 16 NovKutno 16:540 min—
Sun 15 NovKutno 16:540 min—
Sat 14 NovKutno 16:540 min—
Fri 13 NovKutno 16:550 min—
Thu 12 NovKutno 16:540 min—
Wed 11 NovKutno 16:54+1 min+2 min
Tue 10 NovKutno 17:33+39 min+39 min
Mon 9 NovKutno 17:33+39 min+39 min
Sun 8 NovKutno 16:540 min—
Sat 7 NovKutno 16:540 min—
Fri 6 NovKutno 16:540 min—
Thu 5 NovKutno 16:540 min—
Wed 4 NovKutno 16:540 min—
Tue 3 NovKutno 16:59+4 min+4 min
Mon 2 NovKutno 16:58+4 min+4 min
Sun 1 NovKutno 17:05+11 min+11 min
Sat 31 OctKutno 16:550 min—
Fri 30 OctKutno 16:540 min—
Thu 29 OctKutno 17:05+11 min+11 min
Wed 28 OctKutno 17:04+10 min+10 min
Tue 27 OctKutno 16:540 min—
Mon 26 OctKutno 16:550 min—
Sun 25 OctKutno 16:54No data—
Sat 24 OctKutno 16:55No data—
Fri 23 OctKutno 16:56No data—
Thu 22 OctKutno 16:56No data—
Wed 21 OctKutno 16:56No data—
Tue 20 OctKutno 16:55No data—