AR 55463 Serock – Tuchola
Alerts for train 55463
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 23:49 from Serock · Sat 7 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
- Fri 4 Sept Max en route +50 min · last fix heading to Wudzyn +50 min
- Thu 3 Sept Max en route +48 min · last fix heading to Wudzyn +48 min
- Sat 10 Oct Max en route +32 min · last fix heading to Tuchola +32 min
- Sun 11 Oct Max en route +30 min · last fix heading to Tuchola +30 min
- Mon 31 Aug Max en route +14 min · last fix heading to Cekcyn +14 min
Distribution · 90 days
24 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 42% · 10
- 3–10 min 33% · 8
- 10–30 min 8% · 2
- 30+ min 17% · 4
On-time by weekday
- 33% M n=6
- 67% T n=3
- 50% W n=2
- 33% T n=3
- 0% F n=2
- 40% S n=5
- 67% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 24 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 |
|---|---|---|---|
| 23:49 | +1 min | +29 min | |
| 23:51 / 23:52 | ≈ +1 min | ≈ +29 min | |
| 23:55 | ≈ +2 min | ≈ +30 min | |
| 23:58 / 23:59 | ≈ +3 min | ≈ +30 min | |
| 00:02 | ≈ +4 min | ≈ +30 min | |
| 00:09 | ≈ +4 min | ≈ +30 min | |
| 00:12 / 00:13 | ≈ +4 min | ≈ +30 min | |
| 00:17 / 00:18 | ≈ +4 min | ≈ +30 min | |
| 00:26 | ≈ +4 min | ≈ +31 min | |
| 00:31 | +5 min | +31 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 | Tuchola 00:33 | No data | — |
| Thu 5 Nov | Tuchola 00:32 | No data | — |
| Wed 4 Nov | Tuchola 00:32 | No data | — |
| Tue 3 Nov | Tuchola 00:32 | No data | — |
| Mon 2 Nov | Tuchola 00:44 | +13 min | +17 min |
| Sun 1 Nov | Tuchola 00:32 | No data | — |
| Sat 31 Oct | Tuchola 00:40 | +7 min | +7 min |
| Fri 30 Oct | Tuchola 00:32 | No data | — |
| Thu 29 Oct | Tuchola 00:32 | No data | — |
| Wed 28 Oct | Tuchola 00:32 | No data | — |
| Tue 27 Oct | Tuchola 00:32 | No data | — |
| Mon 26 Oct | Tuchola 00:33 | 0 min | — |
| Sun 25 Oct | Tuchola 00:32 | No data | — |
| Sat 24 Oct | Tuchola 00:06 | No data | — |
| Fri 23 Oct | Tuchola 00:07 | No data | — |
| Thu 22 Oct | Tuchola 00:06 | No data | — |
| Wed 21 Oct | Tuchola 00:06 | No data | — |
| Tue 20 Oct | Tuchola 00:06 | No data | — |
| Mon 19 Oct | Tuchola 00:06 | No data | — |
| Sun 18 Oct | Tuchola 00:07 | 0 min | — |
| Sat 17 Oct | Tuchola 00:06 | 0 min | — |
| Fri 16 Oct | Tuchola 00:06 | No data | — |
| Thu 15 Oct | Tuchola 00:07 | No data | — |
| Wed 14 Oct | Tuchola 00:07 | No data | — |
| Tue 13 Oct | Tuchola 00:07 | +1 min | +1 min |
| Mon 12 Oct | Tuchola 00:13 | +7 min | +7 min |
| Sun 11 Oct | Tuchola 00:36 | +30 min | +30 min |
| Sat 10 Oct | Tuchola 00:37 | +32 min | +32 min |
| Fri 9 Oct | Tuchola 00:06 | No data | — |
| Thu 8 Oct | Tuchola 00:06 | 0 min | +5 min |