R31 51340 Sierpc – Płock

View line R31

Sierpc 04:31 → Płock 05:05 Mon, Tue, Wed, Thu, Fri, Sat 0 h 34 min · 6 stops Koleje Mazowieckie

✓ Today’s run finished

Today it reached Płock at 05:05 0 min

  1. Sierpc04:31
  2. Susk04:37
  3. Gozdowo04:43
  4. Proboszczewice Płockie04:50
  5. Płock Trzepowo04:59
  6. Płock05:05

Next service: tomorrow 04:31 from Sierpc · Fri 13 Nov

Full trip card
Next departure 04:31 tomorrow · Sierpc
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 5 no data
On-time · 90 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Sat 12 Sept Max en route +9 min · last fix heading to Płock Trzepowo +9 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 97% · 28
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=5
  • 100% W n=4
  • 100% T n=5
  • 100% F n=4
  • 80% S n=5
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
Sierpc
04:31on time on time
Susk
04:37≈ on time ≈ on time
Gozdowo
04:43≈ on time ≈ on time
Proboszczewice Płockie
04:50 / 04:51≈ on time ≈ on time
Płock Trzepowo
04:59≈ on time ≈ on time
Płock
05:05on time on time

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 12 NovPłock 05:040 min—
Tue 10 NovPłock 05:040 min—
Mon 9 NovPłock 05:040 min—
Sat 7 NovPłock 05:040 min—
Fri 6 NovPłock 05:040 min—
Thu 5 NovPłock 05:040 min—
Wed 4 NovPłock 05:07+1 min+1 min
Tue 3 NovPłock 05:040 min—
Mon 2 NovPłock 05:040 min+6 min
Sat 31 OctPłock 05:060 min—
Fri 30 OctPłock 05:060 min—
Thu 29 OctPłock 05:060 min—
Wed 28 OctPłock 05:060 min—
Tue 27 OctPłock 05:070 min—
Mon 26 OctPłock 05:060 min—
Sat 24 OctPłock 05:06No data—
Fri 23 OctPłock 05:06No data—
Thu 22 OctPłock 05:06No data—
Wed 21 OctPłock 05:06No data—
Tue 20 OctPłock 05:06No data—
Mon 19 OctPłock 05:060 min—
Sat 17 OctPłock 05:060 min—
Fri 16 OctPłock 05:070 min—
Thu 15 OctPłock 05:060 min—
Wed 14 OctPłock 05:060 min—
Tue 13 OctPłock 05:060 min—
Mon 12 OctPłock 05:060 min—
Sat 10 OctPłock 05:060 min—
Fri 9 OctPłock 05:060 min—
Thu 8 OctPłock 05:070 min—