R31 19221 Kutno – Płock

View line R31

Kutno 04:46 → Płock 05:36 Daily 0 h 50 min · 10 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Płock at 05:36 −1 min

  1. Kutno04:46
  2. Raciborów Kutnowski04:54
  3. Strzelce Kujawskie04:58
  4. Gostynin05:10
  5. Rogożew05:15
  6. Płock Radziwie05:27
  7. Płock05:36

Next service: tomorrow 04:46 from Kutno · Fri 6 Nov

Next departure 04:46 tomorrow · Kutno
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
91%
29/32 runs under 3 min
RT coverage: 32 full · 0 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: +2 min

Last 30 days

Arrival delay at Płock, 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 Płock +10 min
  • Thu 29 Oct Max en route +4 min · last fix heading to Płock +4 min
  • Thu 10 Sept Max en route +3 min · last fix heading to Płock +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 29
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=5
  • 67% T n=6
  • 100% F n=4
  • 100% S n=4
  • 67% S n=3

Stops and timetable

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

Last 90 days, 32 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:46on time +2 min
04:49≈ on time ≈ +2 min
04:54≈ on time ≈ +2 min
04:58 / 04:59≈ on time ≈ +2 min
05:04≈ on time ≈ +2 min
05:10 / 05:11≈ on time ≈ +2 min
05:15≈ on time ≈ +2 min
05:20≈ on time ≈ +2 min
05:27≈ on time ≈ +2 min
05:36on 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 5 NovPłock 05:37−1 min—
Wed 4 NovPłock 05:370 min—
Tue 3 NovPłock 05:38+1 min+1 min
Mon 2 NovPłock 05:370 min—
Sun 1 NovPłock 05:48+10 min+10 min
Sat 31 OctPłock 05:370 min—
Fri 30 OctPłock 05:370 min—
Thu 29 OctPłock 05:41+4 min+4 min
Wed 28 OctPłock 05:370 min—
Tue 27 OctPłock 05:380 min—
Mon 26 OctPłock 05:370 min—
Sun 25 OctPłock 05:37No data—
Sat 24 OctPłock 05:37No data—
Fri 23 OctPłock 05:37No data—
Thu 22 OctPłock 05:37No data—
Wed 21 OctPłock 05:37No data—
Tue 20 OctPłock 05:37No data—
Mon 19 OctPłock 05:370 min—
Sun 18 OctPłock 05:370 min—
Sat 17 OctPłock 05:370 min—
Fri 16 OctPłock 05:380 min—
Thu 15 OctPłock 05:36−1 min—
Wed 14 OctPłock 05:370 min—
Tue 13 OctPłock 05:370 min—
Mon 12 OctPłock 05:370 min—
Sun 11 OctPłock 05:36−1 min—
Sat 10 OctPłock 05:370 min—
Fri 9 OctPłock 05:370 min—
Thu 8 OctPłock 05:380 min—
Wed 7 OctPłock 05:39+2 min+2 min