AR 50263 Serock – Tuchola
Alerts for train 50263
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 Tuchola at 12:27 No data
- Serock11:38
- Świekatowo11:44
- Lipienica11:47
- Wierzchucin11:58
- Wierzchucin Stary12:07
- Tuchola Rudzki Most12:21
- Tuchola12:26
Next service: tomorrow 11:38 from Serock · Fri 6 Nov
Last 30 days
Arrival delay at Tuchola, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 23 Sept Max en route +6 min · last fix heading to Tuchola Rudzki Most +6 min
- Mon 12 Oct Max en route +5 min · last fix heading to Tuchola +5 min
- Mon 28 Sept Max en route +5 min · last fix heading to Tuchola Rudzki Most +5 min
- Fri 25 Sept Max en route +5 min · last fix heading to Tuchola Rudzki Most +5 min
- Sun 1 Nov Max en route +4 min · last fix heading to Tuchola +4 min
Distribution · 90 days
18 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 56% · 10
- 3–10 min 44% · 8
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=6
- 75% T n=4
- 67% W n=3
- 67% T n=3
- 0% F n=1
- — S n=0
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 18 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 |
|---|---|---|---|
| 11:38 | on time | +5 min | |
| 11:40 / 11:41 | ≈ on time | ≈ +5 min | |
| 11:44 | ≈ on time | ≈ +5 min | |
| 11:47 / 11:48 | ≈ on time | ≈ +5 min | |
| 11:51 | ≈ on time | ≈ +5 min | |
| 11:58 / 12:04 | ≈ on time | ≈ +5 min | |
| 12:07 / 12:08 | ≈ on time | ≈ +5 min | |
| 12:12 / 12:13 | ≈ on time | ≈ +5 min | |
| 12:21 / 12:22 | ≈ on time | ≈ +5 min | |
| 12:26 | +1 min | +5 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 5 Nov | Tuchola 12:27 | No data | — |
| Wed 4 Nov | Tuchola 12:27 | No data | — |
| Tue 3 Nov | Tuchola 12:27 | No data | — |
| Mon 2 Nov | Tuchola 12:27 | 0 min | — |
| Sun 1 Nov | Tuchola 12:32 | +4 min | +4 min |
| Fri 30 Oct | Tuchola 12:27 | No data | — |
| Thu 29 Oct | Tuchola 12:27 | 0 min | — |
| Wed 28 Oct | Tuchola 12:27 | 0 min | — |
| Tue 27 Oct | Tuchola 12:27 | 0 min | — |
| Mon 26 Oct | Tuchola 12:28 | 0 min | — |
| Fri 23 Oct | Tuchola 12:47 | No data | — |
| Thu 22 Oct | Tuchola 12:47 | No data | — |
| Wed 21 Oct | Tuchola 12:47 | No data | — |
| Tue 20 Oct | Tuchola 12:48 | No data | — |
| Mon 19 Oct | Tuchola 12:47 | No data | — |
| Fri 16 Oct | Tuchola 12:47 | No data | — |
| Thu 15 Oct | Tuchola 12:47 | No data | — |
| Wed 14 Oct | Tuchola 12:48 | No data | — |
| Tue 13 Oct | Tuchola 12:48 | +1 min | +1 min |
| Mon 12 Oct | Tuchola 12:52 | +5 min | +5 min |
| Fri 9 Oct | Tuchola 12:47 | No data | — |
| Thu 8 Oct | Tuchola 12:47 | 0 min | — |
| Wed 7 Oct | Tuchola 12:47 | 0 min | — |
| Tue 6 Oct | Tuchola 12:47 | 0 min | — |
| Mon 5 Oct | Tuchola 12:47 | 0 min | — |
| Fri 2 Oct | Tuchola 12:45 | No data | — |
| Thu 1 Oct | Tuchola 12:45 | No data | — |
| Wed 30 Sept | Tuchola 12:45 | No data | — |
| Tue 29 Sept | Tuchola 12:46 | No data | — |
| Mon 28 Sept | Tuchola Rudzki Most 12:46 | +5 min | +5 min |