R31 91218 Płock – Kutno
Alerts for train 91218
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R31.
It does not run today
Last recorded run: Friday 13 November 0 min
Next service: Monday 19:50 from Płock · Mon 16 Nov
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
- Fri 18 Sept Max en route +18 min · last fix heading to Sierakówek +18 min
- Tue 10 Nov Max en route +16 min · last fix heading to Kutno +16 min
- Mon 9 Nov Max en route +16 min · last fix heading to Kutno +16 min
- Tue 3 Nov Max en route +6 min · last fix heading to Kutno +6 min
- Mon 2 Nov Max en route +6 min · last fix heading to Kutno +6 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 71% · 27
- 3–10 min 21% · 8
- 10–30 min 8% · 3
- 30+ min 0% · 0
On-time by weekday
- 57% M n=7
- 63% T n=8
- 83% W n=6
- 75% T n=8
- 78% 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, 38 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 19:50 | +1 min | +5 min | |
| 19:58 / 19:59 | ≈ +1 min | ≈ +5 min | |
| 20:05 | ≈ +1 min | ≈ +5 min | |
| 20:09 | ≈ +1 min | ≈ +6 min | |
| 20:14 / 20:20 | ≈ +1 min | ≈ +6 min | |
| 20:26 | ≈ +1 min | ≈ +6 min | |
| 20:31 / 20:32 | ≈ +1 min | ≈ +6 min | |
| 20:36 | ≈ +1 min | ≈ +6 min | |
| 20:41 | ≈ +1 min | ≈ +6 min | |
| 20:45 | +1 min | +6 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 13 Nov | Kutno 20:47 | 0 min | — |
| Thu 12 Nov | Kutno 20:44 | 0 min | — |
| Tue 10 Nov | Kutno 21:02 | +16 min | +16 min |
| Mon 9 Nov | Kutno 21:02 | +16 min | +16 min |
| Fri 6 Nov | Kutno 20:48 | +2 min | +2 min |
| Thu 5 Nov | Kutno 20:48 | +1 min | +1 min |
| Wed 4 Nov | Kutno 20:44 | 0 min | — |
| Tue 3 Nov | Kutno 20:53 | +6 min | +6 min |
| Mon 2 Nov | Kutno 20:52 | +6 min | +6 min |
| Fri 30 Oct | Kutno 20:48 | +2 min | +2 min |
| Thu 29 Oct | Kutno 20:51 | +5 min | +5 min |
| Wed 28 Oct | Kutno 20:52 | +6 min | +6 min |
| Tue 27 Oct | Kutno 20:46 | 0 min | — |
| Mon 26 Oct | Kutno 20:47 | 0 min | — |
| Fri 23 Oct | Kutno 20:47 | No data | — |
| Thu 22 Oct | Kutno 20:46 | No data | — |
| Wed 21 Oct | Kutno 20:46 | No data | — |
| Tue 20 Oct | Kutno 20:46 | No data | — |
| Mon 19 Oct | Kutno 20:46 | No data | — |
| Fri 16 Oct | Kutno 20:47 | 0 min | — |
| Thu 15 Oct | Kutno 20:46 | −1 min | — |
| Wed 14 Oct | Kutno 20:46 | 0 min | — |
| Tue 13 Oct | Kutno 20:47 | +1 min | +1 min |
| Mon 12 Oct | Kutno 20:47 | +1 min | +1 min |
| Fri 9 Oct | Kutno 20:46 | 0 min | — |
| Thu 8 Oct | Kutno 20:47 | 0 min | — |
| Wed 7 Oct | Kutno 20:46 | 0 min | — |
| Tue 6 Oct | Kutno 20:46 | 0 min | — |
| Mon 5 Oct | Kutno 20:46 | 0 min | — |
| Fri 2 Oct | Kutno 20:45 | +3 min | +3 min |