REG 95874 Malbork – Grudziądz
Alerts for train 95874
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line REG.
✓ Today’s run finished
Today it reached Grudziądz at 16:58 0 min
- Malbork15:47
- Sztum15:59
- Ryjewo16:09
- Sadlinki16:27
- Gardeja16:37
- Grudziądz Owczarki16:49
- Grudziądz16:58
Next service: tomorrow 15:47 from Malbork · Sat 14 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 1 Nov Max en route +5 min · last fix heading to Grudziądz +5 min
Distribution · 90 days
34 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 97% · 33
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=5
- 100% T n=5
- 100% F n=5
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 34 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 |
|---|---|---|---|
| 15:47 | on time | on time | |
| 15:53 / 15:54 | ≈ on time | ≈ on time | |
| 15:59 | ≈ on time | ≈ on time | |
| 16:02 / 16:03 | ≈ on time | ≈ on time | |
| 16:09 | ≈ on time | ≈ on time | |
| 16:13 | ≈ on time | ≈ on time | |
| 16:20 / 16:21 | ≈ on time | ≈ on time | |
| 16:27 / 16:28 | ≈ on time | ≈ on time | |
| 16:33 | ≈ on time | ≈ on time | |
| 16:37 / 16:38 | ≈ on time | ≈ on time | |
| 16:43 / 16:44 | ≈ on time | ≈ on time | |
| 16:49 / 16:50 | ≈ on time | ≈ on time | |
| 16:52 / 16:53 | ≈ on time | ≈ on time | |
| 16:58 | on time | on time |
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 13 Nov | Grudziądz 17:00 | 0 min | — |
| Thu 12 Nov | Grudziądz 16:59 | 0 min | — |
| Wed 11 Nov | Grudziądz 16:59 | 0 min | — |
| Tue 10 Nov | Grudziądz 16:59 | 0 min | — |
| Mon 9 Nov | Grudziądz 16:59 | 0 min | — |
| Sun 8 Nov | Grudziądz 16:59 | 0 min | — |
| Sat 7 Nov | Grudziądz 16:59 | 0 min | — |
| Fri 6 Nov | Grudziądz 16:59 | 0 min | — |
| Thu 5 Nov | Grudziądz 16:59 | 0 min | — |
| Wed 4 Nov | Grudziądz 16:59 | 0 min | — |
| Tue 3 Nov | Grudziądz 16:59 | 0 min | — |
| Mon 2 Nov | Grudziądz 16:59 | 0 min | — |
| Sun 1 Nov | Grudziądz 17:05 | +5 min | +5 min |
| Sat 31 Oct | Grudziądz 17:00 | 0 min | — |
| Fri 30 Oct | Grudziądz 16:59 | 0 min | — |
| Thu 29 Oct | Grudziądz 16:59 | 0 min | — |
| Wed 28 Oct | Grudziądz 16:59 | 0 min | — |
| Tue 27 Oct | Grudziądz 16:59 | 0 min | — |
| Mon 26 Oct | Grudziądz 17:00 | 0 min | — |
| Sun 25 Oct | Grudziądz 16:59 | No data | — |
| Sat 24 Oct | Grudziądz 16:59 | No data | — |
| Fri 23 Oct | Grudziądz 17:00 | No data | — |
| Thu 22 Oct | Grudziądz 17:00 | No data | — |
| Wed 21 Oct | Grudziądz 17:00 | No data | — |
| Tue 20 Oct | Grudziądz 16:59 | No data | — |
| Mon 19 Oct | Grudziądz 16:59 | No data | — |
| Sun 18 Oct | Grudziądz 17:00 | 0 min | — |
| Sat 17 Oct | Grudziądz 17:00 | 0 min | — |
| Fri 16 Oct | Grudziądz 16:59 | 0 min | — |
| Thu 15 Oct | Grudziądz 16:59 | 0 min | — |