R91 59861 Nasielsk – Sierpc
Alerts for train 59861
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R91.
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 05:34 from Nasielsk · Thu 5 Nov
Last 30 days
Arrival delay at Sierpc, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
19 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 19
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=4
- 100% W n=4
- 100% T n=3
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 19 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 |
|---|---|---|---|
| 05:34 | on time | on time | |
| 05:40 / 05:41 | ≈ on time | ≈ on time | |
| 05:47 | ≈ on time | ≈ on time | |
| 05:53 | ≈ on time | ≈ on time | |
| 06:00 / 06:15 | ≈ on time | ≈ on time | |
| 06:20 | ≈ on time | ≈ on time | |
| 06:24 / 06:25 | ≈ on time | ≈ on time | |
| 06:30 / 06:31 | ≈ on time | ≈ on time | |
| 06:37 | ≈ on time | ≈ on time | |
| 06:43 | ≈ on time | ≈ on time | |
| 06:49 | ≈ on time | ≈ on time | |
| 06:52 | ≈ on time | ≈ on time | |
| 06:57 / 06:58 | ≈ on time | ≈ on time | |
| 07:04 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Sierpc 07:04 | 0 min | — |
| Tue 3 Nov | Sierpc 07:04 | 0 min | — |
| Mon 2 Nov | Sierpc 07:04 | 0 min | — |
| Fri 30 Oct | Sierpc 07:05 | 0 min | — |
| Thu 29 Oct | Sierpc 07:05 | 0 min | — |
| Wed 28 Oct | Sierpc 07:05 | 0 min | — |
| Tue 27 Oct | Sierpc 07:05 | 0 min | — |
| Mon 26 Oct | Sierpc 07:05 | 0 min | — |
| Fri 23 Oct | Sierpc 07:05 | No data | — |
| Thu 22 Oct | Sierpc 07:05 | No data | — |
| Wed 21 Oct | Sierpc 07:05 | No data | — |
| Tue 20 Oct | Sierpc 07:05 | No data | — |
| Mon 19 Oct | Sierpc 07:05 | 0 min | — |
| Fri 16 Oct | Sierpc 07:05 | 0 min | — |
| Thu 15 Oct | Sierpc 07:05 | 0 min | — |
| Wed 14 Oct | Sierpc 07:05 | 0 min | — |
| Tue 13 Oct | Sierpc 07:05 | 0 min | — |
| Mon 12 Oct | Sierpc 07:06 | 0 min | — |
| Fri 9 Oct | Sierpc 07:06 | 0 min | — |
| Thu 8 Oct | Sierpc 07:05 | 0 min | — |
| Wed 7 Oct | Sierpc 07:06 | 0 min | — |
| Tue 6 Oct | Sierpc 07:06 | 0 min | — |
| Mon 5 Oct | Sierpc 07:06 | 0 min | — |
| Fri 2 Oct | Sierpc 07:03 | No data | — |
| Thu 1 Oct | Sierpc 07:03 | No data | — |
| Wed 30 Sept | Sierpc 07:04 | No data | — |
| Tue 29 Sept | Sierpc 07:03 | No data | — |
| Mon 28 Sept | Sierpc 07:03 | No data | — |
| Fri 25 Sept | Sierpc 07:03 | No data | — |
| Thu 24 Sept | Sierpc 07:03 | No data | — |