REG 95873 Kwidzyn – Malbork
Alerts for train 95873
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.
It has not run yet today
Last recorded run: Monday 9 November 0 min
Next service: today 16:33 from Kwidzyn · Tue 10 Nov
Last 30 days
Arrival delay at Malbork, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 14 Sept Max en route +7 min · last fix heading to Malbork +7 min
- Sun 27 Sept Max en route +3 min · last fix heading to Malbork +3 min
Distribution · 90 days
30 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 93% · 28
- 3–10 min 7% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 83% M n=6
- 100% T n=3
- 100% W n=4
- 100% T n=4
- 100% F n=4
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 30 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 |
|---|---|---|---|
| 16:33 | on time | +2 min | |
| 16:39 / 16:40 | ≈ on time | ≈ +2 min | |
| 16:44 | ≈ on time | ≈ +2 min | |
| 16:50 | ≈ on time | ≈ +2 min | |
| 16:54 / 17:00 | ≈ on time | ≈ +2 min | |
| 17:04 / 17:05 | ≈ on time | ≈ +2 min | |
| 17:13 | 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 |
|---|---|---|---|
| Mon 9 Nov | Malbork 17:14 | 0 min | — |
| Sun 8 Nov | Malbork 17:14 | 0 min | — |
| Sat 7 Nov | Malbork 17:14 | 0 min | — |
| Fri 6 Nov | Malbork 17:14 | 0 min | — |
| Thu 5 Nov | Malbork 17:14 | +2 min | +2 min |
| Wed 4 Nov | Malbork 17:14 | 0 min | — |
| Tue 3 Nov | Malbork 17:15 | 0 min | — |
| Mon 2 Nov | Malbork 17:14 | 0 min | — |
| Sun 1 Nov | Malbork 17:14 | No data | — |
| Sat 31 Oct | Malbork 17:15 | No data | — |
| Fri 30 Oct | Malbork 17:14 | No data | — |
| Thu 29 Oct | Malbork 17:14 | No data | — |
| Wed 28 Oct | Malbork 17:14 | No data | — |
| Tue 27 Oct | Malbork 17:14 | No data | — |
| Mon 26 Oct | Malbork 17:15 | 0 min | — |
| Sun 25 Oct | Malbork 17:14 | No data | — |
| Sat 24 Oct | Malbork 17:04 | No data | — |
| Fri 23 Oct | Malbork 17:05 | No data | — |
| Thu 22 Oct | Malbork 17:04 | No data | — |
| Wed 21 Oct | Malbork 17:05 | No data | — |
| Tue 20 Oct | Malbork 17:04 | No data | — |
| Mon 19 Oct | Malbork 17:04 | No data | — |
| Sun 18 Oct | Malbork 17:05 | 0 min | — |
| Sat 17 Oct | Malbork 17:05 | 0 min | — |
| Fri 16 Oct | Malbork 17:04 | 0 min | — |
| Thu 15 Oct | Malbork 17:04 | 0 min | — |
| Wed 14 Oct | Malbork 17:04 | 0 min | — |
| Tue 13 Oct | Malbork 17:05 | 0 min | — |
| Mon 12 Oct | Malbork 17:04 | 0 min | — |
| Sun 11 Oct | Malbork 17:04 | 0 min | — |