R31 91202 Płock – Kutno
Alerts for train 91202
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.
✓ Today’s run finished
Today it reached Kutno at 08:13 0 min
- Płock07:18
- Łąck07:33
- Rogożew07:37
- Sierakówek07:48
- Strzelce Kujawskie07:54
- Kutno Azory08:09
- Kutno08:13
Next service: tomorrow 07:18 from Płock · Sun 8 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
- Wed 28 Oct Max en route +12 min · last fix heading to Kutno +12 min
- Sun 1 Nov Max en route +4 min · last fix heading to Kutno +4 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 34
- 3–10 min 3% · 1
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=4
- 75% W n=4
- 100% T n=5
- 100% F n=5
- 100% S n=7
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 07:18 | on time | +1 min | |
| 07:26 / 07:27 | ≈ on time | ≈ +1 min | |
| 07:33 | ≈ on time | ≈ +1 min | |
| 07:37 | ≈ on time | ≈ +1 min | |
| 07:42 | ≈ on time | ≈ +1 min | |
| 07:48 | ≈ on time | ≈ +1 min | |
| 07:54 / 08:00 | ≈ on time | ≈ +1 min | |
| 08:04 | ≈ on time | ≈ +1 min | |
| 08:09 | ≈ on time | ≈ +1 min | |
| 08:13 | on time | +1 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 |
|---|---|---|---|
| Sat 7 Nov | Kutno 08:14 | 0 min | — |
| Fri 6 Nov | Kutno 08:14 | 0 min | — |
| Thu 5 Nov | Kutno 08:14 | 0 min | — |
| Wed 4 Nov | Kutno 08:14 | +1 min | +1 min |
| Tue 3 Nov | Kutno 08:14 | +2 min | +2 min |
| Mon 2 Nov | Kutno 08:14 | 0 min | — |
| Sun 1 Nov | Kutno 08:19 | +4 min | +4 min |
| Sat 31 Oct | Kutno 08:14 | 0 min | — |
| Fri 30 Oct | Kutno 08:14 | 0 min | — |
| Thu 29 Oct | Kutno 08:14 | 0 min | — |
| Wed 28 Oct | Kutno 08:26 | +12 min | +12 min |
| Tue 27 Oct | Kutno 08:14 | 0 min | — |
| Mon 26 Oct | Kutno 08:14 | 0 min | — |
| Sun 25 Oct | Kutno 08:14 | No data | — |
| Sat 24 Oct | Kutno 08:13 | No data | — |
| Fri 23 Oct | Kutno 08:13 | No data | — |
| Thu 22 Oct | Kutno 08:13 | No data | — |
| Wed 21 Oct | Kutno 08:13 | No data | — |
| Tue 20 Oct | Kutno 08:13 | No data | — |
| Mon 19 Oct | Kutno 08:13 | 0 min | — |
| Sun 18 Oct | Kutno 08:13 | 0 min | — |
| Sat 17 Oct | Kutno 08:13 | 0 min | — |
| Fri 16 Oct | Kutno 08:13 | 0 min | — |
| Thu 15 Oct | Kutno 08:13 | 0 min | — |
| Wed 14 Oct | Kutno 08:13 | 0 min | — |
| Tue 13 Oct | Kutno 08:13 | 0 min | — |
| Mon 12 Oct | Kutno 08:13 | 0 min | — |
| Sun 11 Oct | Kutno 08:13 | 0 min | — |
| Sat 10 Oct | Kutno 08:13 | 0 min | — |
| Fri 9 Oct | Kutno 08:15 | +1 min | +1 min |