REG 80446 Ustka Uroczysko – Słupsk

View line REG

Ustka Uroczysko 19:17 → Słupsk 19:38 Daily 0 h 21 min · 7 stops PKP

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 19:17 from Ustka Uroczysko · Thu 5 Nov

Next departure 19:17 today · Ustka Uroczysko
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
82%
23/28 runs under 3 min
RT coverage: 28 full · 0 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

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

  • Mon 26 Oct Max en route +8 min · last fix heading to Słupsk +8 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Słupsk +8 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Słupsk +4 min
  • Tue 1 Sept Max en route +3 min · last fix heading to Słupsk Północny +3 min
  • Mon 31 Aug Max en route +3 min · last fix heading to Słupsk Północny +3 min

Distribution · 90 days

28 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 4% · 1
  • On time 79% · 22
  • 3–10 min 18% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 80% T n=5
  • 100% W n=5
  • 100% T n=2
  • 100% F n=3
  • 75% S n=4
  • 75% S n=4

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 stops).

Last 90 days, 28 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.

StopSched.Usually 9 days in 10
19:17on time +3 min
19:19≈ on time ≈ +3 min
19:25≈ on time ≈ +3 min
19:27 / 19:28≈ on time ≈ +3 min
19:30≈ on time ≈ +3 min
19:34 / 19:35≈ on time ≈ +3 min
19:38on time +3 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

DateLast stopFinalMax
Wed 4 NovSłupsk 19:390 min—
Tue 3 NovSłupsk 19:390 min—
Mon 2 NovSłupsk 19:37−2 min—
Sun 1 NovSłupsk 19:47+8 min+8 min
Sat 31 OctSłupsk 19:44+4 min+4 min
Fri 30 OctSłupsk 19:39No data—
Thu 29 OctSłupsk 19:40No data—
Wed 28 OctSłupsk 19:390 min—
Tue 27 OctSłupsk 19:390 min—
Mon 26 OctSłupsk 19:48+8 min+8 min
Sun 25 OctSłupsk 19:39No data—
Sat 24 OctSłupsk 19:40No data—
Fri 23 OctSłupsk 19:40No data—
Thu 22 OctSłupsk 19:39No data—
Wed 21 OctSłupsk 19:39No data—
Tue 20 OctSłupsk 19:39No data—
Mon 19 OctSłupsk 19:39No data—
Sun 18 OctSłupsk 19:390 min—
Sat 17 OctSłupsk 19:390 min—
Fri 16 OctSłupsk 19:400 min—
Thu 15 OctSłupsk 19:42+2 min+2 min
Wed 14 OctSłupsk 19:390 min—
Tue 13 OctSłupsk 19:390 min—
Mon 12 OctSłupsk 19:390 min—
Sun 11 OctSłupsk 19:390 min—
Sat 10 OctSłupsk 19:390 min—
Fri 9 OctSłupsk 19:390 min—
Thu 8 OctSłupsk 19:390 min—
Wed 7 OctSłupsk 19:390 min—
Tue 6 OctSłupsk 19:390 min—