REG 80448 Ustka Uroczysko – Słupsk

View line REG

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 20:24 from Ustka Uroczysko · Wed 18 Nov

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

  • Tue 27 Oct Max en route +18 min · last fix heading to Słupsk +18 min
  • Thu 15 Oct Max en route +13 min · last fix heading to Słupsk +13 min
  • Sun 15 Nov Max en route +10 min · last fix heading to Słupsk +10 min
  • Sun 27 Sept Max en route +10 min · last fix heading to Gałęzinowo +10 min
  • Sat 26 Sept Max en route +10 min · last fix heading to Gałęzinowo +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 60% · 30
  • 3–10 min 30% · 15
  • 10–30 min 10% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 71% T n=7
  • 50% W n=8
  • 43% T n=7
  • 50% F n=6
  • 63% S n=8
  • 57% S n=7

Stops and timetable

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

Last 90 days, 50 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
20:24+2 min +7 min
20:26≈ +2 min ≈ +7 min
20:32≈ +2 min ≈ +7 min
20:34 / 20:35≈ +2 min ≈ +7 min
20:37≈ +2 min ≈ +7 min
20:41 / 20:42≈ +2 min ≈ +7 min
20:45+2 min +7 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
Tue 17 NovSłupsk 20:440 min—
Mon 16 NovSłupsk 20:440 min—
Sun 15 NovSłupsk 20:54+10 min+10 min
Sat 14 NovSłupsk 20:52+6 min+6 min
Fri 13 NovSłupsk 20:470 min—
Thu 12 NovSłupsk 20:440 min—
Wed 11 NovSłupsk 20:440 min—
Tue 10 NovSłupsk 20:47+1 min+1 min
Mon 9 NovSłupsk 20:48+2 min+2 min
Sun 8 NovSłupsk 20:440 min—
Sat 7 NovSłupsk 20:440 min—
Fri 6 NovSłupsk 20:440 min—
Thu 5 NovSłupsk 20:49+3 min+3 min
Wed 4 NovSłupsk 20:440 min—
Tue 3 NovSłupsk 20:470 min—
Mon 2 NovSłupsk 20:440 min—
Sun 1 NovSłupsk 20:49+4 min+4 min
Sat 31 OctSłupsk 20:470 min—
Fri 30 OctSłupsk 20:46No data—
Thu 29 OctSłupsk 20:46No data—
Wed 28 OctSłupsk 20:53+7 min+7 min
Tue 27 OctSłupsk 21:04+18 min+18 min
Mon 26 OctSłupsk 20:52+5 min+5 min
Sun 25 OctSłupsk 20:46No data—
Sat 24 OctSłupsk 20:47No data—
Fri 23 OctSłupsk 20:47No data—
Thu 22 OctSłupsk 20:46No data—
Wed 21 OctSłupsk 20:46No data—
Tue 20 OctSłupsk 20:46No data—
Mon 19 OctSłupsk 20:46No data—