AR 50328 Chojnice – Serock
Alerts for train 50328
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line AR.
It has not run yet today
Last recorded run: Friday 6 November No data
Next service: today 16:28 from Chojnice · Mon 9 Nov
Last 30 days
Arrival delay at Serock, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 2 Nov Max en route +50 min · last fix heading to Serock +50 min
- Fri 25 Sept Max en route +5 min · last fix heading to Rynkowo Wiadukt +5 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 8
- 3–10 min 10% · 1
- 10–30 min 0% · 0
- 30+ min 10% · 1
On-time by weekday
- 80% M n=5
- 100% T n=2
- 100% W n=1
- 100% T n=1
- 0% F n=1
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (15 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 16:28 | on time | +8 min | |
| 16:34 | ≈ on time | ≈ +8 min | |
| 16:38 / 16:39 | ≈ on time | ≈ +9 min | |
| 16:42 / 16:43 | ≈ on time | ≈ +9 min | |
| 16:46 | ≈ on time | ≈ +9 min | |
| 16:53 / 16:55 | ≈ on time | ≈ +9 min | |
| 16:58 | ≈ on time | ≈ +9 min | |
| 17:07 | ≈ on time | ≈ +9 min | |
| 17:12 | ≈ on time | ≈ +9 min | |
| 17:16 / 17:17 | ≈ on time | ≈ +9 min | |
| 17:23 / 17:24 | ≈ on time | ≈ +9 min | |
| 17:27 | ≈ on time | ≈ +9 min | |
| 17:31 | ≈ on time | ≈ +9 min | |
| 17:35 | ≈ on time | ≈ +9 min | |
| 17:40 | on time | +10 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 |
|---|---|---|---|
| Fri 6 Nov | Serock 17:40 | No data | — |
| Thu 5 Nov | Serock 17:39 | No data | — |
| Wed 4 Nov | Serock 17:39 | No data | — |
| Tue 3 Nov | Serock 17:40 | No data | — |
| Mon 2 Nov | Serock 18:29 | +50 min | +50 min |
| Sun 1 Nov | Serock 17:41 | No data | — |
| Fri 30 Oct | Serock 17:41 | No data | — |
| Thu 29 Oct | Serock 17:41 | No data | — |
| Wed 28 Oct | Serock 17:41 | No data | — |
| Tue 27 Oct | Serock 17:41 | No data | — |
| Mon 26 Oct | Serock 17:42 | 0 min | — |
| Fri 23 Oct | Bydgoszcz Główna 18:17 | No data | — |
| Thu 22 Oct | Bydgoszcz Główna 18:17 | No data | — |
| Wed 21 Oct | Bydgoszcz Główna 18:16 | No data | — |
| Tue 20 Oct | Bydgoszcz Główna 18:16 | No data | — |
| Fri 16 Oct | Bydgoszcz Główna 18:17 | No data | — |
| Thu 15 Oct | Bydgoszcz Główna 18:16 | No data | — |
| Wed 14 Oct | Bydgoszcz Główna 18:16 | No data | — |
| Tue 13 Oct | Bydgoszcz Główna 18:16 | 0 min | +8 min |
| Mon 12 Oct | Bydgoszcz Główna 18:16 | 0 min | — |
| Fri 9 Oct | Bydgoszcz Główna 18:16 | No data | — |
| Thu 8 Oct | Bydgoszcz Główna 18:17 | 0 min | — |
| Wed 7 Oct | Bydgoszcz Główna 18:16 | 0 min | — |
| Tue 6 Oct | Bydgoszcz Główna 18:16 | 0 min | — |
| Mon 5 Oct | Bydgoszcz Główna 18:16 | 0 min | — |
| Fri 2 Oct | Bydgoszcz Główna 18:15 | No data | — |
| Thu 1 Oct | Bydgoszcz Główna 18:14 | No data | — |
| Wed 30 Sept | Bydgoszcz Główna 18:15 | No data | — |
| Tue 29 Sept | Bydgoszcz Główna 18:14 | No data | — |
| Mon 28 Sept | Bydgoszcz Główna 18:14 | No data | — |