Ł 97635 Łódź Widzew → Zgierz

View line Ł

Łódź Widzew 15:51 → Zgierz 16:10 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 7 stops ŁKA

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 15:51 from Łódź Widzew · Mon 23 Nov

Next departure 15:51 Monday · Łódź Widzew
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 24 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 Zgierz, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 10% · 3
  • On time 90% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=5
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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:51on time on time
15:54≈ on time ≈ on time
15:57 / 15:59≈ on time ≈ on time
16:01≈ on time ≈ on time
16:03≈ on time ≈ on time
16:05 / 16:06≈ on time ≈ on time
16:10on 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
Fri 20 NovZgierz 16:120 min—
Thu 19 NovZgierz 16:13+2 min+2 min
Wed 18 NovZgierz 16:13+2 min+2 min
Tue 17 NovZgierz 16:090 min—
Mon 16 NovZgierz 16:090 min—
Fri 13 NovZgierz 16:090 min—
Thu 12 NovZgierz 16:090 min—
Tue 10 NovZgierz 16:090 min—
Mon 9 NovZgierz 16:090 min—
Fri 6 NovZgierz 16:090 min—
Thu 5 NovZgierz 16:09−2 min—
Wed 4 NovZgierz 16:090 min—
Tue 3 NovZgierz 16:100 min—
Mon 2 NovZgierz 16:090 min—
Fri 30 OctZgierz 16:110 min—
Thu 29 OctZgierz 16:110 min—
Wed 28 OctZgierz 16:110 min—
Tue 27 OctZgierz 16:110 min—
Mon 26 OctZgierz 16:120 min—
Fri 23 OctZgierz 16:11No data—
Thu 22 OctZgierz 16:12No data—
Wed 21 OctZgierz 16:12No data—
Tue 20 OctZgierz 16:11No data—
Mon 19 OctZgierz 16:12No data—
Fri 16 OctZgierz 16:110 min—
Thu 15 OctZgierz 16:110 min—
Wed 14 OctZgierz 16:110 min—
Tue 13 OctZgierz 16:10−2 min—
Mon 12 OctZgierz 16:110 min—
Fri 9 OctZgierz 16:110 min—