REG 88904 Słupsk – Miastko
Alerts for train 88904
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 Miastko at 11:27 0 min
- Słupsk10:12
- Widzino10:20
- Wrząca Pomorska10:30
- Kępice10:43
- Biesowice11:02
- Przytocko11:11
- Miastko11:27
Next service: tomorrow 10:12 from Słupsk · Wed 11 Nov
Last 30 days
Arrival delay at Miastko, 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 26 Sept Max en route +5 min · last fix heading to Miastko +5 min
- Sat 12 Sept Max en route +4 min · last fix heading to Miastko +4 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 30
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=5
- 100% W n=3
- 100% T n=4
- 100% F n=5
- 67% S n=6
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (13 stops).
Last 90 days, 32 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 |
|---|---|---|---|
| 10:12 | on time | on time | |
| 10:17 / 10:18 | ≈ on time | ≈ on time | |
| 10:20 / 10:21 | ≈ on time | ≈ on time | |
| 10:25 / 10:26 | ≈ on time | ≈ on time | |
| 10:30 | ≈ on time | ≈ on time | |
| 10:35 / 10:36 | ≈ on time | ≈ on time | |
| 10:43 / 10:56 | ≈ on time | ≈ on time | |
| 10:59 | ≈ on time | ≈ on time | |
| 11:02 / 11:03 | ≈ on time | ≈ on time | |
| 11:06 | ≈ on time | ≈ on time | |
| 11:11 / 11:12 | ≈ on time | ≈ on time | |
| 11:17 / 11:18 | ≈ on time | ≈ on time | |
| 11:27 | 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 |
|---|---|---|---|
| Tue 10 Nov | Miastko 11:28 | 0 min | — |
| Mon 9 Nov | Miastko 11:28 | 0 min | — |
| Sun 8 Nov | Miastko 11:29 | 0 min | — |
| Sat 7 Nov | Miastko 11:28 | 0 min | — |
| Fri 6 Nov | Miastko 11:28 | 0 min | — |
| Thu 5 Nov | Miastko 11:28 | 0 min | — |
| Wed 4 Nov | Miastko 11:28 | 0 min | — |
| Tue 3 Nov | Miastko 11:28 | 0 min | — |
| Mon 2 Nov | Miastko 11:28 | 0 min | — |
| Sun 1 Nov | Miastko 11:28 | No data | — |
| Sat 31 Oct | Miastko 11:28 | 0 min | — |
| Fri 30 Oct | Miastko 11:28 | 0 min | — |
| Thu 29 Oct | Miastko 11:28 | 0 min | — |
| Wed 28 Oct | Miastko 11:28 | 0 min | — |
| Tue 27 Oct | Miastko 11:28 | 0 min | — |
| Mon 26 Oct | Miastko 11:28 | 0 min | — |
| Sun 25 Oct | Miastko 11:28 | No data | — |
| Sat 24 Oct | Miastko 11:22 | No data | — |
| Fri 23 Oct | Miastko 11:22 | No data | — |
| Thu 22 Oct | Miastko 11:22 | No data | — |
| Wed 21 Oct | Miastko 11:22 | No data | — |
| Tue 20 Oct | Miastko 11:22 | No data | — |
| Mon 19 Oct | Miastko 11:22 | 0 min | — |
| Sun 18 Oct | Miastko 11:22 | 0 min | — |
| Sat 17 Oct | Miastko 11:22 | 0 min | — |
| Fri 16 Oct | Miastko 11:22 | 0 min | — |
| Thu 15 Oct | Miastko 11:22 | 0 min | — |
| Wed 14 Oct | Miastko 11:23 | No data | — |
| Tue 13 Oct | Miastko 11:22 | 0 min | — |
| Mon 12 Oct | Miastko 11:22 | 0 min | — |