REG 80438 Ustka Uroczysko – Słupsk

View line REG

Ustka Uroczysko 14:56 → Słupsk 15:17 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 14:56 from Ustka Uroczysko · Thu 5 Nov

Next departure 14:56 today · Ustka Uroczysko
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
88%
22/25 runs under 3 min
RT coverage: 25 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 22
  • 3–10 min 12% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=2
  • 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, 25 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
14:56on time +2 min
14:58≈ on time ≈ +2 min
15:04≈ on time ≈ +2 min
15:06 / 15:07≈ on time ≈ +2 min
15:09≈ on time ≈ +2 min
15:13 / 15:14≈ on time ≈ +2 min
15:17on 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

DateLast stopFinalMax
Wed 4 NovSłupsk 15:180 min—
Tue 3 NovSłupsk 15:180 min—
Mon 2 NovSłupsk 15:180 min—
Sun 1 NovSłupsk 15:22+4 min+4 min
Sat 31 OctSłupsk 15:190 min—
Fri 30 OctSłupsk 15:18No data—
Thu 29 OctSłupsk 15:180 min—
Wed 28 OctSłupsk 15:180 min—
Tue 27 OctSłupsk 15:180 min—
Mon 26 OctSłupsk 15:22+3 min+3 min
Sun 25 OctSłupsk 15:18No data—
Sat 24 OctSłupsk 15:20No data—
Fri 23 OctSłupsk 15:20No data—
Thu 22 OctSłupsk 15:20No data—
Wed 21 OctSłupsk 15:21No data—
Tue 20 OctSłupsk 15:20No data—
Mon 19 OctSłupsk 15:21No data—
Sun 18 OctSłupsk 15:200 min—
Sat 17 OctSłupsk 15:210 min—
Fri 16 OctSłupsk 15:200 min—
Thu 15 OctSłupsk 15:200 min—
Wed 14 OctSłupsk 15:200 min—
Tue 13 OctSłupsk 15:210 min—
Mon 12 OctSłupsk 15:200 min—
Sun 11 OctSłupsk 15:200 min—
Sat 10 OctSłupsk 15:210 min—
Fri 9 OctSłupsk 15:200 min—
Thu 8 OctSłupsk 15:200 min—
Wed 7 OctSłupsk 15:200 min—
Tue 6 OctSłupsk 15:200 min—