R31 91200 Płock – Kutno

View line R31

Płock 06:28 → Kutno 07:19 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 10 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Kutno at 07:20 +1 min

  1. Płock06:28
  2. Łąck06:43
  3. Rogożew06:49
  4. Sierakówek07:00
  5. Strzelce Kujawskie07:05
  6. Kutno Azory07:15
  7. Kutno07:19

Next service: tomorrow 06:28 from Płock · Tue 17 Nov

Next departure 06:28 tomorrow · Płock
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 4 no data
On-time · 90 days
90%
38/42 runs under 3 min
RT coverage: 42 full · 0 partial · 13 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Wed 28 Oct Max en route +39 min · last fix heading to Kutno +39 min
  • Tue 13 Oct Max en route +4 min · last fix heading to Kutno +4 min
  • Mon 12 Oct Max en route +4 min · last fix heading to Kutno +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Kutno +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 38
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 90% M n=10
  • 88% T n=8
  • 83% W n=6
  • 89% T n=9
  • 100% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 42 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
06:28+1 min +2 min
06:36 / 06:37≈ +1 min ≈ +2 min
06:43 / 06:45≈ +1 min ≈ +2 min
06:49≈ +1 min ≈ +2 min
06:54≈ +1 min ≈ +2 min
07:00≈ +1 min ≈ +2 min
07:05 / 07:06≈ +1 min ≈ +2 min
07:10≈ +1 min ≈ +2 min
07:15≈ +1 min ≈ +2 min
07:19+1 min +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
Mon 16 NovKutno 07:19+1 min+1 min
Fri 13 NovKutno 07:190 min—
Thu 12 NovKutno 07:190 min—
Tue 10 NovKutno 07:190 min—
Mon 9 NovKutno 07:190 min—
Fri 6 NovKutno 07:190 min—
Thu 5 NovKutno 07:190 min—
Wed 4 NovKutno 07:190 min—
Tue 3 NovKutno 07:190 min—
Mon 2 NovKutno 07:19+1 min+1 min
Fri 30 OctKutno 07:200 min—
Thu 29 OctKutno 07:23+3 min+3 min
Wed 28 OctKutno 07:59+39 min+39 min
Tue 27 OctKutno 07:200 min—
Mon 26 OctKutno 07:200 min+1 min
Fri 23 OctKutno 07:18No data—
Thu 22 OctKutno 07:18No data—
Wed 21 OctKutno 07:18No data—
Tue 20 OctKutno 07:18No data—
Mon 19 OctKutno 07:19+1 min+1 min
Fri 16 OctKutno 07:180 min—
Thu 15 OctKutno 07:180 min—
Wed 14 OctKutno 07:20+2 min+2 min
Tue 13 OctKutno 07:22+4 min+4 min
Mon 12 OctKutno 07:23+4 min+4 min
Fri 9 OctKutno 07:21+2 min+2 min
Thu 8 OctKutno 07:180 min—
Wed 7 OctKutno 07:190 min—
Tue 6 OctKutno 07:190 min—
Mon 5 OctKutno 07:19+1 min+1 min