R62 11787 Ostrołęka – Chorzele
Alerts for train 11787
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line R62.
It has not run yet today
Last recorded run: Sunday 8 November 0 min
Next service: today 15:42 from Ostrołęka · Mon 9 Nov
Last 30 days
Arrival delay at Chorzele, 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 25 Sept Max en route +9 min · last fix heading to Raszujka +9 min
Distribution · 90 days
20 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 19
- 3–10 min 5% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=3
- 100% T n=4
- 67% F n=3
- — S n=0
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 20 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:42 | on time | on time | |
| 15:48 | ≈ on time | ≈ on time | |
| 15:55 | ≈ on time | ≈ on time | |
| 16:00 | ≈ on time | ≈ on time | |
| 16:07 / 16:08 | ≈ on time | ≈ on time | |
| 16:15 | ≈ on time | ≈ on time | |
| 16:22 | ≈ on time | ≈ on time | |
| 16:27 | ≈ on time | ≈ on time | |
| 16:33 | 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 |
|---|---|---|---|
| Sun 8 Nov | Chorzele 16:34 | 0 min | — |
| Fri 6 Nov | Chorzele 16:34 | 0 min | — |
| Thu 5 Nov | Chorzele 16:34 | 0 min | — |
| Wed 4 Nov | Chorzele 16:34 | 0 min | — |
| Tue 3 Nov | Chorzele 16:35 | No data | — |
| Mon 2 Nov | Chorzele 16:34 | 0 min | — |
| Sun 1 Nov | Chorzele 16:34 | No data | — |
| Fri 30 Oct | Chorzele 16:34 | No data | — |
| Thu 29 Oct | Chorzele 16:34 | 0 min | — |
| Wed 28 Oct | Chorzele 16:34 | 0 min | — |
| Tue 27 Oct | Chorzele 16:34 | 0 min | — |
| Mon 26 Oct | Chorzele 16:35 | 0 min | — |
| Sun 25 Oct | Chorzele 16:34 | No data | — |
| Fri 23 Oct | Chorzele 16:35 | No data | — |
| Thu 22 Oct | Chorzele 16:35 | No data | — |
| Wed 21 Oct | Chorzele 16:35 | No data | — |
| Tue 20 Oct | Chorzele 16:34 | No data | — |
| Mon 19 Oct | Chorzele 16:34 | No data | — |
| Sun 18 Oct | Chorzele 16:34 | 0 min | — |
| Fri 16 Oct | Chorzele 16:34 | 0 min | — |
| Thu 15 Oct | Chorzele 16:34 | 0 min | — |
| Wed 14 Oct | Chorzele 16:34 | No data | — |
| Tue 13 Oct | Chorzele 16:35 | 0 min | — |
| Mon 12 Oct | Chorzele 16:34 | 0 min | — |
| Sun 11 Oct | Chorzele 16:34 | No data | — |
| Fri 9 Oct | Chorzele 16:34 | No data | — |
| Thu 8 Oct | Chorzele 16:34 | 0 min | — |
| Wed 7 Oct | Chorzele 16:34 | 0 min | — |
| Tue 6 Oct | Chorzele 16:34 | 0 min | — |
| Mon 5 Oct | Chorzele 16:35 | 0 min | — |