AR 50259 Serock – Chojnice
Alerts for train 50259
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.
✓ Today’s run finished
Today, last fix heading to Chojnice at 10:29 No data
- Serock09:02
- Świekatowo09:09
- Wierzchucin09:25
- Cekcyn09:34
- Tuchola09:46
- Silno10:13
- Chojnice10:28
Next service: tomorrow 09:02 from Serock · Fri 13 Nov
Last 30 days
Arrival delay at Chojnice, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 24 Sept Max en route +32 min · last fix heading to Tuchola +32 min
- Fri 25 Sept Max en route +24 min · last fix heading to Żalno +24 min
- Tue 13 Oct Max en route +7 min · last fix heading to Chojnice +3 min
Distribution · 90 days
12 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 75% · 9
- 3–10 min 8% · 1
- 10–30 min 8% · 1
- 30+ min 8% · 1
On-time by weekday
- 100% M n=6
- 50% T n=2
- 100% W n=1
- 50% T n=2
- 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, 12 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 |
|---|---|---|---|
| 09:02 | on time | +20 min | |
| 09:05 | ≈ on time | ≈ +20 min | |
| 09:09 | ≈ on time | ≈ +21 min | |
| 09:13 | ≈ on time | ≈ +21 min | |
| 09:17 / 09:18 | ≈ on time | ≈ +21 min | |
| 09:25 / 09:26 | ≈ on time | ≈ +22 min | |
| 09:29 | ≈ on time | ≈ +22 min | |
| 09:34 | ≈ on time | ≈ +22 min | |
| 09:42 / 09:43 | ≈ on time | ≈ +22 min | |
| 09:46 / 10:00 | ≈ on time | ≈ +22 min | |
| 10:05 / 10:06 | ≈ on time | ≈ +22 min | |
| 10:09 | ≈ on time | ≈ +22 min | |
| 10:13 / 10:16 | ≈ on time | ≈ +22 min | |
| 10:19 / 10:20 | ≈ on time | ≈ +22 min | |
| 10:28 | on time | +22 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 |
|---|---|---|---|
| Thu 12 Nov | Chojnice 10:29 | No data | — |
| Tue 10 Nov | Chojnice 10:29 | No data | — |
| Mon 9 Nov | Chojnice 10:30 | 0 min | +1 min |
| Fri 6 Nov | Chojnice 10:29 | No data | — |
| Thu 5 Nov | Chojnice 10:29 | No data | — |
| Wed 4 Nov | Chojnice 10:29 | No data | — |
| Tue 3 Nov | Chojnice 10:29 | No data | — |
| Mon 2 Nov | Chojnice 10:29 | 0 min | — |
| Sun 1 Nov | Chojnice 10:30 | No data | — |
| Fri 30 Oct | Chojnice 10:29 | No data | — |
| Thu 29 Oct | Chojnice 10:29 | No data | — |
| Wed 28 Oct | Chojnice 10:29 | No data | — |
| Tue 27 Oct | Chojnice 10:29 | No data | — |
| Mon 26 Oct | Chojnice 10:29 | 0 min | — |
| Fri 23 Oct | Chojnice 10:07 | No data | — |
| Thu 22 Oct | Chojnice 10:07 | No data | — |
| Wed 21 Oct | Chojnice 10:07 | No data | — |
| Tue 20 Oct | Chojnice 10:07 | No data | — |
| Mon 19 Oct | Chojnice 10:09 | 0 min | — |
| Fri 16 Oct | Chojnice 10:07 | No data | — |
| Thu 15 Oct | Chojnice 10:07 | No data | — |
| Wed 14 Oct | Chojnice 10:07 | No data | — |
| Tue 13 Oct | Chojnice 10:10 | +3 min | +7 min |
| Mon 12 Oct | Chojnice 10:07 | 0 min | — |
| Fri 9 Oct | Chojnice 10:08 | No data | — |
| Thu 8 Oct | Chojnice 10:07 | 0 min | — |
| Wed 7 Oct | Chojnice 10:07 | 0 min | — |
| Tue 6 Oct | Chojnice 10:07 | 0 min | — |
| Mon 5 Oct | Chojnice 10:08 | 0 min | +4 min |
| Fri 2 Oct | Chojnice 10:05 | No data | — |