KW 71208 Konin – Kutno

View line KW

Konin 05:10 → Kutno 06:06 Daily 0 h 56 min · 11 stops Koleje Wielkopolskie

Running now · updated 05:38

Position estimated from the timetable

Between Barłogi and Kłodawa 0 min

Estimated arrival at Kutno 06:06 · 28 km/h

  1. Konin05:10
  2. Kramsk05:20
  3. Budki Nowe05:25
  4. Barłogi05:37
  5. Kłodawa05:43
  6. Turzynów05:50
  7. Kutno06:06

Today it is running no worse than usual: typical arrival delay is 0 min; 96% of the last 23 runs arrived on time.

On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
95%
36/38 runs under 3 min
RT coverage: 37 full · 1 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Wed 2 Sept Max en route +12 min · last fix heading to Krzewie +12 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Kutno +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 92% · 35
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 83% W n=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 38 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 10Today
05:10on time +2 minPassed
05:15 / 05:16≈ on time ≈ +2 minPassed
05:20 / 05:21≈ on time ≈ +2 minPassed
05:25≈ on time ≈ +2 minPassed
05:30 / 05:31≈ on time ≈ +2 minPassed
05:37 / 05:38≈ on time ≈ +2 minPassed
05:43 / 05:44≈ on time ≈ +2 minNext
05:50≈ on time ≈ +2 min
05:56 / 05:57≈ on time ≈ +2 min
05:59 / 06:00≈ on time ≈ +2 min
06:06on time +2 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 12 NovBarłogi 05:34Partial coverage0 min—
Wed 11 NovKutno 06:070 min—
Tue 10 NovKutno 06:080 min—
Mon 9 NovKutno 06:08+1 min+1 min
Sun 8 NovKutno 06:09+4 min+4 min
Sat 7 NovKutno 06:080 min—
Fri 6 NovKutno 06:070 min—
Thu 5 NovKutno 06:070 min—
Wed 4 NovKutno 06:070 min—
Tue 3 NovKutno 06:070 min—
Mon 2 NovKutno 06:070 min—
Sun 1 NovKutno 06:08No data—
Sat 31 OctKutno 06:08+1 min+1 min
Fri 30 OctKutno 06:08+1 min+1 min
Thu 29 OctKutno 06:070 min—
Wed 28 OctKutno 06:070 min—
Tue 27 OctKutno 06:070 min—
Mon 26 OctKutno 06:070 min—
Sun 25 OctKutno 06:07No data—
Sat 24 OctKutno 06:07No data—
Fri 23 OctKutno 06:07No data—
Thu 22 OctKutno 06:07No data—
Wed 21 OctKutno 06:07No data—
Tue 20 OctKutno 06:07No data—
Mon 19 OctKutno 06:070 min—
Sun 18 OctKutno 06:080 min—
Sat 17 OctKutno 06:070 min—
Fri 16 OctKutno 06:080 min—
Thu 15 OctKutno 06:08+1 min+1 min
Wed 14 OctKutno 06:070 min—