AR 50412 Laskowice Pomorskie – Grudziądz
Alerts for train 50412
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 Grudziądz at 12:59 No data
- Laskowice Pomorskie12:35
- Jeżewo12:38
- Dubielno12:42
- Dolna Grupa12:50
- Dragacz12:52
- Grudziądz Śródmieście12:55
- Grudziądz12:59
Next service: tomorrow 12:35 from Laskowice Pomorskie · Sat 7 Nov
Last 30 days
Arrival delay at Grudziądz, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 18 Oct Max en route +9 min · last fix heading to Grudziądz +7 min
Distribution · 90 days
11 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 10
- 3–10 min 9% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=2
- 100% W n=2
- 100% T n=2
- — F n=0
- 100% S n=1
- 0% S n=1
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 stops).
Last 90 days, 11 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 |
|---|---|---|---|
| 12:35 | on time | +2 min | |
| 12:38 | ≈ on time | ≈ +2 min | |
| 12:42 | ≈ on time | ≈ +2 min | |
| 12:46 / 12:47 | ≈ on time | ≈ +2 min | |
| 12:50 | ≈ on time | ≈ +2 min | |
| 12:52 / 12:53 | ≈ on time | ≈ +2 min | |
| 12:55 / 12:56 | ≈ on time | ≈ +2 min | |
| 12:59 | on time | +2 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 | Grudziądz 12:59 | No data | — |
| Thu 5 Nov | Grudziądz 12:59 | No data | — |
| Wed 4 Nov | Grudziądz 12:59 | No data | — |
| Tue 3 Nov | Grudziądz 13:00 | No data | — |
| Mon 2 Nov | Grudziądz 12:59 | No data | — |
| Sun 1 Nov | Grudziądz 13:00 | No data | — |
| Sat 31 Oct | Grudziądz 13:31 | 0 min | — |
| Fri 30 Oct | Grudziądz 13:00 | No data | — |
| Thu 29 Oct | Grudziądz 13:00 | No data | — |
| Wed 28 Oct | Grudziądz 13:00 | No data | — |
| Tue 27 Oct | Grudziądz 13:00 | No data | — |
| Mon 26 Oct | Grudziądz 13:00 | 0 min | — |
| Sun 25 Oct | Grudziądz 13:31 | No data | — |
| Sat 24 Oct | Grudziądz 13:19 | No data | — |
| Fri 23 Oct | Grudziądz 13:00 | No data | — |
| Thu 22 Oct | Grudziądz 13:00 | No data | — |
| Wed 21 Oct | Grudziądz 13:00 | No data | — |
| Tue 20 Oct | Grudziądz 13:01 | No data | — |
| Mon 19 Oct | Grudziądz 13:00 | No data | — |
| Sun 18 Oct | Grudziądz 13:27 | +7 min | +9 min |
| Sat 17 Oct | Grudziądz 13:20 | No data | — |
| Fri 16 Oct | Grudziądz 13:00 | No data | — |
| Thu 15 Oct | Grudziądz 13:00 | No data | — |
| Wed 14 Oct | Grudziądz 13:01 | No data | — |
| Tue 13 Oct | Grudziądz 13:01 | +1 min | +1 min |
| Mon 12 Oct | Grudziądz 13:00 | 0 min | — |
| Sun 11 Oct | Grudziądz 13:19 | No data | — |
| Sat 10 Oct | Grudziądz 13:20 | No data | — |
| Fri 9 Oct | Grudziądz 13:00 | No data | — |
| Thu 8 Oct | Grudziądz 13:02 | +2 min | +2 min |