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