R91 95850 Sierpc – Nasielsk
Alerts for train 95850
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 04:13 from Sierpc · Thu 5 Nov
Last 30 days
Arrival delay at Nasielsk, 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 |
|---|---|---|---|
| 04:13 | on time | on time | |
| 04:18 | ≈ on time | ≈ on time | |
| 04:23 / 04:24 | ≈ on time | ≈ on time | |
| 04:26 | ≈ on time | ≈ on time | |
| 04:32 | ≈ on time | ≈ on time | |
| 04:39 | ≈ on time | ≈ on time | |
| 04:45 | ≈ on time | ≈ on time | |
| 04:50 / 04:51 | ≈ on time | ≈ on time | |
| 04:54 / 04:55 | ≈ on time | ≈ on time | |
| 05:01 | ≈ on time | ≈ on time | |
| 05:08 | ≈ on time | ≈ on time | |
| 05:14 | ≈ on time | ≈ on time | |
| 05:20 / 05:21 | ≈ on time | ≈ on time | |
| 05:28 | 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 | Nasielsk 05:29 | 0 min | — |
| Tue 3 Nov | Nasielsk 05:29 | 0 min | — |
| Mon 2 Nov | Nasielsk 05:29 | 0 min | +7 min |
| Fri 30 Oct | Nasielsk 05:29 | 0 min | — |
| Thu 29 Oct | Nasielsk 05:29 | 0 min | — |
| Wed 28 Oct | Nasielsk 05:29 | 0 min | — |
| Tue 27 Oct | Nasielsk 05:30 | 0 min | — |
| Mon 26 Oct | Nasielsk 05:29 | 0 min | — |
| Fri 23 Oct | Nasielsk 05:29 | No data | — |
| Thu 22 Oct | Nasielsk 05:29 | No data | — |
| Wed 21 Oct | Nasielsk 05:29 | No data | — |
| Tue 20 Oct | Nasielsk 05:29 | No data | — |
| Mon 19 Oct | Nasielsk 05:29 | 0 min | — |
| Fri 16 Oct | Nasielsk 05:30 | 0 min | — |
| Thu 15 Oct | Nasielsk 05:29 | 0 min | — |
| Wed 14 Oct | Nasielsk 05:29 | 0 min | — |
| Tue 13 Oct | Nasielsk 05:29 | 0 min | — |
| Mon 12 Oct | Nasielsk 05:29 | 0 min | — |
| Fri 9 Oct | Nasielsk 05:29 | 0 min | — |
| Thu 8 Oct | Nasielsk 05:30 | 0 min | — |
| Wed 7 Oct | Nasielsk 05:29 | 0 min | — |
| Tue 6 Oct | Nasielsk 05:29 | 0 min | — |
| Mon 5 Oct | Nasielsk 05:30 | 0 min | — |
| Fri 2 Oct | Nasielsk 05:27 | No data | — |
| Thu 1 Oct | Nasielsk 05:27 | No data | — |
| Wed 30 Sept | Nasielsk 05:27 | No data | — |
| Tue 29 Sept | Nasielsk 05:27 | No data | — |
| Mon 28 Sept | Nasielsk 05:27 | No data | — |
| Fri 25 Sept | Nasielsk 05:27 | No data | — |
| Thu 24 Sept | Nasielsk 05:27 | No data | — |