REG 80429 Słupsk – Ustka Uroczysko

View line REG

Słupsk 09:43 → Ustka Uroczysko 10:04 Daily 0 h 21 min · 7 stops PolRegio

✓ Today’s run finished

Today, last fix heading to Ustka Uroczysko at 10:04 No data

  1. Słupsk09:43
  2. Słupsk Północny09:45
  3. Strzelinko09:50
  4. Gałęzinowo09:52
  5. Charnowo Słupskie09:55
  6. Ustka10:01
  7. Ustka Uroczysko10:04

Next service: tomorrow 09:43 from Słupsk · Thu 12 Nov

Next departure 09:43 tomorrow · Słupsk
On-time · 30 days
67%
10/15 runs under 3 min
RT coverage: 15 full · 0 partial · 15 no data
On-time · 90 days
74%
17/23 runs under 3 min
RT coverage: 23 full · 0 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+15min
9 in 10 runs arrive with less than this
30 days: +33 min

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

  • Mon 9 Nov Max en route +45 min · last fix heading to Ustka Uroczysko +45 min
  • Tue 10 Nov Max en route +44 min · last fix heading to Ustka Uroczysko +44 min
  • Thu 29 Oct Max en route +16 min · last fix heading to Ustka Uroczysko +16 min
  • Fri 6 Nov Max en route +9 min · last fix heading to Ustka Uroczysko +9 min
  • Thu 5 Nov Max en route +14 min · last fix heading to Ustka Uroczysko +8 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 74% · 17
  • 3–10 min 13% · 3
  • 10–30 min 4% · 1
  • 30+ min 9% · 2

On-time by weekday

  • 83% M n=6
  • 75% T n=4
  • 100% W n=3
  • 33% T n=3
  • 33% F n=3
  • 100% S n=2
  • 100% S n=2

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.

StopSched.Usually 9 days in 10
09:43on time +5 min
09:45 / 09:46≈ on time ≈ +5 min
09:50≈ on time ≈ +8 min
09:52 / 09:53≈ on time ≈ +9 min
09:55≈ on time ≈ +9 min
10:01≈ on time ≈ +13 min
10:04on time +15 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 11 NovUstka Uroczysko 10:04No data—
Tue 10 NovUstka Uroczysko 10:49+44 min+44 min
Mon 9 NovUstka Uroczysko 10:50+45 min+45 min
Sun 8 NovUstka Uroczysko 10:050 min—
Sat 7 NovUstka Uroczysko 10:04No data—
Fri 6 NovUstka Uroczysko 10:14+9 min+9 min
Thu 5 NovUstka Uroczysko 10:13+8 min+14 min
Wed 4 NovUstka Uroczysko 10:040 min—
Tue 3 NovUstka Uroczysko 10:040 min—
Mon 2 NovUstka Uroczysko 10:040 min—
Sun 1 NovUstka Uroczysko 10:06No data—
Sat 31 OctUstka Uroczysko 10:050 min—
Fri 30 OctUstka Uroczysko 10:05No data—
Thu 29 OctUstka Uroczysko 10:21+16 min+16 min
Wed 28 OctUstka Uroczysko 10:05No data—
Tue 27 OctUstka Uroczysko 10:05No data—
Mon 26 OctUstka Uroczysko 10:050 min—
Sun 25 OctUstka Uroczysko 10:05No data—
Sat 24 OctUstka Uroczysko 10:07No data—
Fri 23 OctUstka Uroczysko 10:07No data—
Thu 22 OctUstka Uroczysko 10:07No data—
Wed 21 OctUstka Uroczysko 10:07No data—
Tue 20 OctUstka Uroczysko 10:07No data—
Mon 19 OctUstka Uroczysko 10:070 min—
Sun 18 OctUstka Uroczysko 10:070 min—
Sat 17 OctUstka Uroczysko 10:07No data—
Fri 16 OctUstka Uroczysko 10:07No data—
Thu 15 OctUstka Uroczysko 10:07No data—
Wed 14 OctUstka Uroczysko 10:070 min—
Tue 13 OctUstka Uroczysko 10:070 min—