REG 51200 Toruń Główny – Kutno

View line REG

Toruń Główny 04:15 → Kutno 05:41 Daily 1 h 26 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Kutno at 05:41 0 min

  1. Toruń Główny04:15
  2. Otłoczyn04:26
  3. Nieszawa Waganiec04:40
  4. Włocławek Zazamcze04:55
  5. Gołaszewo Kujawskie05:08
  6. Kaliska Kujawskie05:21
  7. Kutno05:41

Next service: tomorrow 04:15 from Toruń Główny · Wed 11 Nov

Next departure 04:15 tomorrow · Toruń Główny
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
65%
32/49 runs under 3 min
RT coverage: 49 full · 0 partial · 23 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
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

  • Sat 12 Sept Max en route +54 min · last fix heading to Lubanie +54 min
  • Mon 28 Sept Max en route +34 min · last fix heading to Gołaszewo Kujawskie +34 min
  • Sun 27 Sept Max en route +34 min · last fix heading to Gołaszewo Kujawskie +34 min
  • Sun 1 Nov Max en route +12 min · last fix heading to Kutno +12 min
  • Sat 26 Sept Max en route +5 min · last fix heading to Kutno +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 32
  • 3–10 min 27% · 13
  • 10–30 min 2% · 1
  • 30+ min 6% · 3

On-time by weekday

  • 78% M n=9
  • 88% T n=8
  • 50% W n=6
  • 57% T n=7
  • 57% F n=7
  • 67% S n=6
  • 50% S n=6

Stops and timetable

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

Last 90 days, 49 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
04:15+1 min +6 min
04:19 / 04:20≈ +1 min ≈ +6 min
04:22≈ +1 min ≈ +6 min
04:26 / 04:27≈ +1 min ≈ +6 min
04:30≈ +1 min ≈ +6 min
04:35≈ +1 min ≈ +6 min
04:40 / 04:41≈ +1 min ≈ +5 min
04:46 / 04:47≈ +1 min ≈ +5 min
04:51≈ +1 min ≈ +5 min
04:55 / 04:56≈ +1 min ≈ +5 min
04:59 / 05:00≈ +1 min ≈ +5 min
05:05≈ +1 min ≈ +5 min
05:08 / 05:09≈ +1 min ≈ +5 min
05:12≈ +1 min ≈ +5 min
05:16≈ +1 min ≈ +5 min
05:21≈ +2 min ≈ +5 min
05:25 / 05:26≈ +2 min ≈ +5 min
05:31 / 05:32≈ +2 min ≈ +5 min
05:41+2 min +5 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
Tue 10 NovKutno 05:430 min—
Mon 9 NovKutno 05:43+1 min+1 min
Sun 8 NovKutno 05:420 min—
Sat 7 NovKutno 05:430 min—
Fri 6 NovKutno 05:44+4 min+4 min
Thu 5 NovKutno 05:44+2 min+2 min
Wed 4 NovKutno 05:420 min—
Tue 3 NovKutno 05:420 min—
Mon 2 NovKutno 05:43+1 min+10 min
Sun 1 NovKutno 05:54+12 min+12 min
Sat 31 OctKutno 05:43+1 min+1 min
Fri 30 OctKutno 05:43+1 min+1 min
Thu 29 OctKutno 05:43+1 min+1 min
Wed 28 OctKutno 05:42No data—
Tue 27 OctKutno 05:44+1 min+1 min
Mon 26 OctKutno 05:41−1 min—
Sun 25 OctKutno 05:42No data—
Sat 24 OctKutno 05:42No data—
Fri 23 OctKutno 05:42No data—
Thu 22 OctKutno 05:42No data—
Wed 21 OctKutno 05:42No data—
Tue 20 OctKutno 05:42No data—
Mon 19 OctKutno 05:420 min—
Sun 18 OctKutno 05:420 min—
Sat 17 OctKutno 05:420 min—
Fri 16 OctKutno 05:42−1 min—
Thu 15 OctKutno 05:42No data—
Wed 14 OctKutno 05:420 min—
Tue 13 OctKutno 05:420 min—
Mon 12 OctKutno 05:430 min—