REG 80433 Słupsk – Ustka Uroczysko

View line REG

Słupsk 11:50 → Ustka Uroczysko 12:11 Daily 0 h 21 min · 7 stops PolRegio

✓ Today’s run finished

Today it reached Ustka Uroczysko at 12:11 0 min

  1. Słupsk11:50
  2. Słupsk Północny11:52
  3. Strzelinko11:57
  4. Gałęzinowo11:59
  5. Charnowo Słupskie12:02
  6. Ustka12:08
  7. Ustka Uroczysko12:11

Next service: tomorrow 11:50 from Słupsk · Fri 6 Nov

Next departure 11:50 tomorrow · Słupsk
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
88%
23/26 runs under 3 min
RT coverage: 26 full · 0 partial · 41 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 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

  • Tue 1 Sept Max en route +5 min · last fix heading to Ustka +5 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Ustka Uroczysko +3 min
  • Sat 3 Oct Max en route +3 min · last fix heading to Ustka +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 80% T n=5
  • 100% W n=4
  • 100% T n=4
  • 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, 26 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
11:50on time +2 min
11:52 / 11:53≈ on time ≈ +2 min
11:57≈ on time ≈ +2 min
11:59 / 12:00≈ on time ≈ +2 min
12:02≈ on time ≈ +2 min
12:08≈ on time ≈ +2 min
12:11on 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
Thu 5 NovUstka Uroczysko 12:120 min—
Wed 4 NovUstka Uroczysko 12:120 min—
Tue 3 NovUstka Uroczysko 12:120 min—
Mon 2 NovUstka Uroczysko 12:12No data—
Sun 1 NovUstka Uroczysko 12:15+3 min+3 min
Sat 31 OctUstka Uroczysko 12:130 min—
Fri 30 OctUstka Uroczysko 12:12No data—
Thu 29 OctUstka Uroczysko 12:120 min—
Wed 28 OctUstka Uroczysko 12:120 min—
Tue 27 OctUstka Uroczysko 12:120 min—
Mon 26 OctUstka Uroczysko 12:120 min—
Sun 25 OctUstka Uroczysko 12:12No data—
Sat 24 OctUstka Uroczysko 12:22No data—
Fri 23 OctUstka Uroczysko 12:22No data—
Thu 22 OctUstka Uroczysko 12:22No data—
Wed 21 OctUstka Uroczysko 12:22No data—
Tue 20 OctUstka Uroczysko 12:23No data—
Mon 19 OctUstka Uroczysko 12:22No data—
Sun 18 OctUstka Uroczysko 12:220 min—
Sat 17 OctUstka Uroczysko 12:220 min—
Fri 16 OctUstka Uroczysko 12:220 min—
Thu 15 OctUstka Uroczysko 12:220 min—
Wed 14 OctUstka Uroczysko 12:230 min—
Tue 13 OctUstka Uroczysko 12:220 min—
Mon 12 OctUstka Uroczysko 12:220 min—
Sun 11 OctUstka Uroczysko 12:220 min—
Sat 10 OctUstka Uroczysko 12:220 min—
Fri 9 OctUstka Uroczysko 12:220 min—
Thu 8 OctUstka Uroczysko 12:220 min—
Wed 7 OctUstka Uroczysko 12:220 min—