R91 95856 Sierpc – Nasielsk
Alerts for train 95856
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 15:51 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
Worst days
- Sun 1 Nov Max en route +8 min · last fix heading to Nasielsk +8 min
- Thu 10 Sept Max en route +6 min · last fix heading to Nasielsk +6 min
- Wed 9 Sept Max en route +6 min · last fix heading to Nasielsk +6 min
- Tue 13 Oct Max en route +3 min · last fix heading to Nasielsk +3 min
- Mon 12 Oct Max en route +3 min · last fix heading to Nasielsk +3 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 25
- 3–10 min 17% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=4
- 75% T n=4
- 83% W n=6
- 80% T n=5
- 100% F n=4
- 100% S n=3
- 75% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 30 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 |
|---|---|---|---|
| 15:51 | on time | +3 min | |
| 15:56 | ≈ on time | ≈ +3 min | |
| 16:01 / 16:02 | ≈ on time | ≈ +3 min | |
| 16:04 | ≈ on time | ≈ +3 min | |
| 16:10 | ≈ on time | ≈ +3 min | |
| 16:17 / 16:23 | ≈ on time | ≈ +3 min | |
| 16:28 | ≈ on time | ≈ +3 min | |
| 16:34 | ≈ on time | ≈ +3 min | |
| 16:38 | ≈ on time | ≈ +3 min | |
| 16:44 / 16:45 | ≈ on time | ≈ +3 min | |
| 16:51 / 16:52 | ≈ on time | ≈ +3 min | |
| 16:58 | ≈ on time | ≈ +3 min | |
| 17:04 | ≈ on time | ≈ +3 min | |
| 17:12 | on time | +3 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 |
|---|---|---|---|
| Wed 4 Nov | Nasielsk 17:13 | 0 min | — |
| Tue 3 Nov | Nasielsk 17:14 | 0 min | — |
| Mon 2 Nov | Nasielsk 17:13 | 0 min | — |
| Sun 1 Nov | Nasielsk 17:21 | +8 min | +8 min |
| Sat 31 Oct | Nasielsk 17:14 | 0 min | — |
| Fri 30 Oct | Nasielsk 17:13 | 0 min | — |
| Thu 29 Oct | Nasielsk 17:13 | 0 min | — |
| Wed 28 Oct | Nasielsk 17:13 | 0 min | — |
| Tue 27 Oct | Nasielsk 17:13 | 0 min | — |
| Mon 26 Oct | Nasielsk 17:14 | 0 min | — |
| Sun 25 Oct | Nasielsk 17:13 | No data | — |
| Sat 24 Oct | Nasielsk 17:12 | No data | — |
| Fri 23 Oct | Nasielsk 17:13 | No data | — |
| Thu 22 Oct | Nasielsk 17:13 | No data | — |
| Wed 21 Oct | Nasielsk 17:13 | No data | — |
| Tue 20 Oct | Nasielsk 17:12 | No data | — |
| Mon 19 Oct | Nasielsk 17:12 | No data | — |
| Sun 18 Oct | Nasielsk 17:13 | 0 min | — |
| Sat 17 Oct | Nasielsk 17:13 | 0 min | — |
| Fri 16 Oct | Nasielsk 17:12 | 0 min | — |
| Thu 15 Oct | Nasielsk 17:12 | 0 min | — |
| Wed 14 Oct | Nasielsk 17:12 | 0 min | — |
| Tue 13 Oct | Nasielsk 17:15 | +3 min | +3 min |
| Mon 12 Oct | Nasielsk 17:15 | +3 min | +3 min |
| Sun 11 Oct | Nasielsk 17:12 | 0 min | — |
| Sat 10 Oct | Nasielsk 17:13 | 0 min | — |
| Fri 9 Oct | Nasielsk 17:12 | 0 min | — |
| Thu 8 Oct | Nasielsk 17:12 | 0 min | — |
| Wed 7 Oct | Nasielsk 17:12 | 0 min | — |
| Tue 6 Oct | Nasielsk 17:12 | 0 min | — |