REG 88925 Miastko – Słupsk
Alerts for train 88925
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: Friday 6 November No data
Next service: today 21:50 from Miastko · Sat 7 Nov
Last 30 days
Arrival delay at Słupsk, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 3 Oct Max en route +38 min · last fix heading to Słupsk +28 min
- Sun 1 Nov Max en route +7 min · last fix heading to Słupsk +7 min
- Sat 10 Oct Max en route +6 min · last fix heading to Słupsk +6 min
- Sun 11 Oct Max en route +5 min · last fix heading to Słupsk +5 min
Distribution · 90 days
21 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 81% · 17
- 3–10 min 14% · 3
- 10–30 min 5% · 1
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=3
- 100% W n=3
- 100% T n=3
- 100% F n=2
- 33% S n=3
- 33% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 21 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 |
|---|---|---|---|
| 21:50 | on time | +5 min | |
| 21:57 / 21:58 | ≈ on time | ≈ +5 min | |
| 22:03 | ≈ on time | ≈ +5 min | |
| 22:08 / 22:09 | ≈ on time | ≈ +5 min | |
| 22:11 / 22:12 | ≈ on time | ≈ +5 min | |
| 22:15 | ≈ on time | ≈ +5 min | |
| 22:18 / 22:19 | ≈ on time | ≈ +5 min | |
| 22:24 / 22:25 | ≈ on time | ≈ +5 min | |
| 22:30 / 22:31 | ≈ on time | ≈ +5 min | |
| 22:35 | ≈ on time | ≈ +5 min | |
| 22:40 | ≈ on time | ≈ +5 min | |
| 22:43 | ≈ on time | ≈ +5 min | |
| 22:50 | on time | +6 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 | Słupsk 22:49 | No data | — |
| Thu 5 Nov | Słupsk 22:49 | No data | — |
| Wed 4 Nov | Słupsk 22:49 | 0 min | — |
| Tue 3 Nov | Słupsk 22:50 | 0 min | — |
| Mon 2 Nov | Słupsk 22:49 | 0 min | — |
| Sun 1 Nov | Słupsk 22:58 | +7 min | +7 min |
| Sat 31 Oct | Słupsk 22:52 | 0 min | — |
| Fri 30 Oct | Słupsk 22:51 | 0 min | — |
| Thu 29 Oct | Słupsk 22:51 | 0 min | — |
| Wed 28 Oct | Słupsk 22:51 | No data | — |
| Tue 27 Oct | Słupsk 22:51 | No data | — |
| Mon 26 Oct | Słupsk 22:52 | 0 min | — |
| Sun 25 Oct | Słupsk 22:51 | No data | — |
| Sat 24 Oct | Słupsk 22:49 | No data | — |
| Fri 23 Oct | Słupsk 22:49 | No data | — |
| Thu 22 Oct | Słupsk 22:48 | No data | — |
| Wed 21 Oct | Słupsk 22:48 | No data | — |
| Tue 20 Oct | Słupsk 22:48 | No data | — |
| Mon 19 Oct | Słupsk 22:48 | No data | — |
| Sun 18 Oct | Słupsk 22:48 | 0 min | — |
| Sat 17 Oct | Słupsk 22:48 | No data | — |
| Fri 16 Oct | Słupsk 22:48 | No data | — |
| Thu 15 Oct | Słupsk 22:49 | 0 min | — |
| Wed 14 Oct | Słupsk 22:49 | 0 min | — |
| Tue 13 Oct | Słupsk 22:48 | 0 min | — |
| Mon 12 Oct | Słupsk 22:48 | 0 min | — |
| Sun 11 Oct | Słupsk 22:53 | +5 min | +5 min |
| Sat 10 Oct | Słupsk 22:54 | +6 min | +6 min |
| Fri 9 Oct | Słupsk 22:48 | 0 min | — |
| Thu 8 Oct | Słupsk 22:48 | 0 min | — |