REG 80442 Ustka Uroczysko – Słupsk

View line REG

Ustka Uroczysko 17:03 → Słupsk 17:24 Daily 0 h 21 min · 7 stops PolRegio

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 17:03 from Ustka Uroczysko · Sun 8 Nov

Next departure 17:03 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
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 4 Nov Max en route +7 min · last fix heading to Słupsk +7 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Słupsk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 75% W n=4
  • 100% T n=4
  • 100% F n=4
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 29 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
17:03on time +1 min
17:05≈ on time ≈ +1 min
17:11≈ on time ≈ +1 min
17:13 / 17:14≈ on time ≈ +1 min
17:16≈ on time ≈ +1 min
17:20 / 17:21≈ on time ≈ +1 min
17:24on time +1 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
Sat 7 NovSłupsk 17:240 min—
Fri 6 NovSłupsk 17:240 min—
Thu 5 NovSłupsk 17:240 min—
Wed 4 NovSłupsk 17:32+7 min+7 min
Tue 3 NovSłupsk 17:240 min—
Mon 2 NovSłupsk 17:240 min—
Sun 1 NovSłupsk 17:29+4 min+4 min
Sat 31 OctSłupsk 17:260 min—
Fri 30 OctSłupsk 17:25No data—
Thu 29 OctSłupsk 17:250 min—
Wed 28 OctSłupsk 17:250 min—
Tue 27 OctSłupsk 17:27+2 min+2 min
Mon 26 OctSłupsk 17:260 min—
Sun 25 OctSłupsk 17:25No data—
Sat 24 OctSłupsk 17:25No data—
Fri 23 OctSłupsk 17:26No data—
Thu 22 OctSłupsk 17:26No data—
Wed 21 OctSłupsk 17:26No data—
Tue 20 OctSłupsk 17:25No data—
Mon 19 OctSłupsk 17:25No data—
Sun 18 OctSłupsk 17:260 min—
Sat 17 OctSłupsk 17:260 min—
Fri 16 OctSłupsk 17:250 min—
Thu 15 OctSłupsk 17:250 min—
Wed 14 OctSłupsk 17:250 min—
Tue 13 OctSłupsk 17:250 min—
Mon 12 OctSłupsk 17:250 min—
Sun 11 OctSłupsk 17:250 min—
Sat 10 OctSłupsk 17:260 min—
Fri 9 OctSłupsk 17:250 min—