R31 91216 Płock – Kutno

View line R31

Płock 18:17 → Kutno 19:16 Daily 0 h 59 min · 10 stops Koleje Mazowieckie

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 18:17 from Płock · Wed 11 Nov

Next departure 18:17 today · Płock
On-time · 30 days
41%
9/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
38%
23/61 runs under 3 min
RT coverage: 61 full · 0 partial · 12 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +4 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Mon 26 Oct Max en route +81 min · last fix heading to Kutno +81 min
  • Thu 8 Oct Max en route +10 min · last fix heading to Kutno +10 min
  • Fri 2 Oct Max en route +10 min · last fix heading to Raciborów Kutnowski +10 min
  • Sat 31 Oct Max en route +9 min · last fix heading to Kutno +9 min
  • Fri 30 Oct Max en route +9 min · last fix heading to Kutno +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 38% · 23
  • 3–10 min 57% · 35
  • 10–30 min 3% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 40% M n=10
  • 33% T n=9
  • 43% W n=7
  • 13% T n=8
  • 33% F n=9
  • 56% S n=9
  • 44% S n=9

Stops and timetable

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

Last 90 days, 61 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
18:17+3 min +7 min
18:25 / 18:26≈ +3 min ≈ +7 min
18:32≈ +3 min ≈ +7 min
18:36≈ +3 min ≈ +7 min
18:41 / 18:42≈ +3 min ≈ +7 min
18:48≈ +3 min ≈ +7 min
18:54 / 19:02≈ +3 min ≈ +7 min
19:07≈ +3 min ≈ +7 min
19:12≈ +3 min ≈ +7 min
19:16+3 min +7 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 19:170 min—
Mon 9 NovKutno 19:170 min—
Sun 8 NovKutno 19:170 min—
Sat 7 NovKutno 19:170 min—
Fri 6 NovKutno 19:19+3 min+3 min
Thu 5 NovKutno 19:22+5 min+5 min
Wed 4 NovKutno 19:19+4 min+4 min
Tue 3 NovKutno 19:23+5 min+5 min
Mon 2 NovKutno 19:19+2 min+2 min
Sun 1 NovKutno 19:19+4 min+4 min
Sat 31 OctKutno 19:27+9 min+9 min
Fri 30 OctKutno 19:26+9 min+9 min
Thu 29 OctKutno 19:23+6 min+6 min
Wed 28 OctKutno 19:24+7 min+7 min
Tue 27 OctKutno 19:18+1 min+1 min
Mon 26 OctKutno 20:39+81 min+81 min
Sun 25 OctKutno 19:17No data—
Sat 24 OctKutno 19:16No data—
Fri 23 OctKutno 19:17No data—
Thu 22 OctKutno 19:16No data—
Wed 21 OctKutno 19:16No data—
Tue 20 OctKutno 19:16No data—
Mon 19 OctKutno 19:16No data—
Sun 18 OctKutno 19:18+2 min+2 min
Sat 17 OctKutno 19:18+2 min+2 min
Fri 16 OctKutno 19:21+4 min+4 min
Thu 15 OctKutno 19:21+4 min+4 min
Wed 14 OctKutno 19:17+1 min+1 min
Tue 13 OctKutno 19:20+4 min+4 min
Mon 12 OctKutno 19:20+4 min+4 min