Ł 97826 Łódź Widzew → Kutno

View line Ł

Łódź Widzew 17:08 → Kutno 18:40 Mon, Tue, Wed, Thu, Fri 1 h 32 min · 22 stops ŁKA

It does not run today

Last recorded run: Friday 20 November +4 min

Next service: Monday 17:08 from Łódź Widzew · Mon 23 Nov

Next departure 17:08 Monday · Łódź Widzew
On-time · 30 days
31%
8/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
31%
20/65 runs under 3 min
RT coverage: 65 full · 0 partial · 18 no data
Typical delay
+5min
Median at arrival, 90 days
30 days: +10 min
P90
+35min
9 in 10 runs arrive with less than this
30 days: +34 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 27 Oct Max en route +112 min · last fix heading to Kutno +112 min
  • Mon 26 Oct Max en route +114 min · last fix heading to Kutno +112 min
  • Thu 8 Oct Max en route +40 min · last fix heading to Kutno +40 min
  • Wed 7 Oct Max en route +40 min · last fix heading to Kutno +40 min
  • Tue 6 Oct Max en route +40 min · last fix heading to Kutno +40 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 31% · 20
  • 3–10 min 38% · 25
  • 10–30 min 17% · 11
  • 30+ min 14% · 9

On-time by weekday

  • 20% M n=10
  • 9% T n=11
  • 44% W n=9
  • 33% T n=9
  • 30% F n=10
  • 38% S n=8
  • 50% S n=8

Stops and timetable

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

Last 90 days, 65 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
17:08+3 min +27 min
17:11 / 17:12≈ +3 min ≈ +27 min
17:14≈ +3 min ≈ +27 min
17:17≈ +3 min ≈ +27 min
17:20 / 17:21≈ +3 min ≈ +29 min
17:25 / 17:26≈ +3 min ≈ +29 min
17:30≈ +3 min ≈ +29 min
17:34≈ +3 min ≈ +29 min
17:38 / 17:39≈ +4 min ≈ +29 min
17:41 / 17:42≈ +4 min ≈ +29 min
17:44 / 17:45≈ +4 min ≈ +29 min
17:47 / 17:48≈ +4 min ≈ +29 min
17:49 / 17:50≈ +4 min ≈ +29 min
17:52≈ +4 min ≈ +29 min
17:56 / 17:57≈ +5 min ≈ +29 min
18:00≈ +5 min ≈ +29 min
18:02≈ +5 min ≈ +29 min
18:06 / 18:07≈ +5 min ≈ +29 min
18:10≈ +5 min ≈ +29 min
18:18≈ +5 min ≈ +30 min
18:25 / 18:30≈ +5 min ≈ +32 min
18:40+5 min +35 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
Fri 20 NovKutno 18:44+4 min+4 min
Thu 19 NovKutno 18:390 min—
Wed 18 NovKutno 18:420 min—
Tue 17 NovKutno 19:09+27 min+27 min
Mon 16 NovKutno 18:59+18 min+18 min
Sun 15 NovKutno 18:53+11 min+11 min
Sat 14 NovKutno 18:53+11 min+11 min
Fri 13 NovKutno 19:12+30 min+30 min
Thu 12 NovKutno 19:12+30 min+30 min
Wed 11 NovKutno 18:390 min—
Tue 10 NovKutno 19:04+23 min+23 min
Mon 9 NovKutno 18:57+15 min+15 min
Sun 8 NovKutno 18:420 min—
Sat 7 NovKutno 18:420 min+1 min
Fri 6 NovKutno 18:44+3 min+3 min
Thu 5 NovKutno 18:49+7 min+7 min
Wed 4 NovKutno 18:49+10 min+10 min
Tue 3 NovKutno 18:50+9 min+9 min
Mon 2 NovKutno 18:49+9 min+9 min
Sun 1 NovKutno 19:19+39 min+39 min
Sat 31 OctKutno 19:05+23 min+23 min
Fri 30 OctKutno 18:43+1 min+1 min
Thu 29 OctKutno 18:420 min—
Wed 28 OctKutno 18:43+1 min+1 min
Tue 27 OctKutno 20:34+112 min+112 min
Mon 26 OctKutno 20:34+112 min+114 min
Sun 25 OctKutno 18:42No data—
Sat 24 OctKutno 18:42No data—
Fri 23 OctKutno 18:43No data—
Thu 22 OctKutno 18:43No data—