REG 51206 Inowrocław – Kutno

View line REG

Inowrocław 11:33 → Kutno 13:35 Mon, Tue, Wed, Thu, Fri 2 h 02 min · 25 stops PolRegio

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 11:33 from Inowrocław · Mon 16 Nov

Next departure 11:33 today · Inowrocław
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 1 Nov Max en route +10 min · last fix heading to Kutno +10 min
  • Thu 1 Oct Max en route +5 min · last fix heading to Kutno +5 min
  • Wed 30 Sept Max en route +5 min · last fix heading to Kutno +5 min
  • Fri 6 Nov Max en route +4 min · last fix heading to Kutno +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 29 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
11:33on time +2 min
11:37≈ on time ≈ +2 min
11:41≈ on time ≈ +3 min
11:44≈ on time ≈ +3 min
11:48≈ on time ≈ +3 min
11:57≈ on time ≈ +3 min
12:03 / 12:06≈ on time ≈ +3 min
12:10 / 12:11≈ on time ≈ +3 min
12:12 / 12:13≈ on time ≈ +3 min
12:17 / 12:18≈ on time ≈ +3 min
12:21≈ on time ≈ +3 min
12:26≈ on time ≈ +3 min
12:31 / 12:32≈ on time ≈ +4 min
12:37≈ on time ≈ +4 min
12:41 / 12:42≈ on time ≈ +4 min
12:46≈ on time ≈ +4 min
12:50 / 12:54≈ on time ≈ +4 min
12:59≈ on time ≈ +4 min
13:02 / 13:03≈ on time ≈ +4 min
13:06≈ on time ≈ +4 min
13:10≈ on time ≈ +4 min
13:15≈ on time ≈ +4 min
13:19 / 13:20≈ on time ≈ +4 min
13:25 / 13:26≈ on time ≈ +4 min
13:35on time +4 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 13 NovKutno 13:340 min—
Thu 12 NovKutno 13:340 min—
Wed 11 NovKutno 13:340 min—
Tue 10 NovKutno 13:340 min—
Mon 9 NovKutno 13:340 min—
Fri 6 NovKutno 13:39+4 min+4 min
Thu 5 NovKutno 13:340 min—
Wed 4 NovKutno 13:340 min—
Tue 3 NovKutno 13:340 min—
Mon 2 NovKutno 13:340 min—
Sun 1 NovKutno 13:46+10 min+10 min
Fri 30 OctKutno 13:35−1 min—
Thu 29 OctKutno 13:360 min—
Wed 28 OctKutno 13:360 min—
Tue 27 OctKutno 13:360 min—
Mon 26 OctKutno 13:360 min—
Fri 23 OctKutno 13:36No data—
Thu 22 OctKutno 13:36No data—
Wed 21 OctKutno 13:36No data—
Tue 20 OctKutno 13:37No data—
Mon 19 OctKutno 13:36No data—
Fri 16 OctKutno 13:360 min—
Thu 15 OctKutno 13:360 min—
Wed 14 OctKutno 13:360 min—
Tue 13 OctKutno 13:360 min—
Mon 12 OctKutno 13:35−1 min—
Fri 9 OctKutno 13:360 min—
Thu 8 OctKutno 13:35−1 min—
Wed 7 OctKutno 13:36−1 min—
Tue 6 OctKutno 13:35−1 min—