REG 88614 Szczecin Główny – Nowogard

View line REG

Szczecin Główny 22:59 → Nowogard 00:03 Mon, Tue, Wed, Thu, Sun 1 h 04 min · 13 stops PolRegio

It has not run yet today

Last recorded run: Sunday 15 November +3 min

Next service: today 22:59 from Szczecin Główny · Mon 16 Nov

Next departure 22:59 today · Szczecin Główny
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 14 full · 0 partial · 6 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 8 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: +3 min

Last 30 days

Arrival delay at Nowogard, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +6 min · last fix heading to Nowogard +6 min
  • Sun 15 Nov Max en route +3 min · last fix heading to Nowogard +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 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=4
  • 100% T n=5
  • — F n=0
  • — S n=0
  • 67% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
22:59on time +1 min
23:10 / 23:11≈ on time ≈ +1 min
23:14 / 23:15≈ on time ≈ +1 min
23:19 / 23:20≈ on time ≈ +2 min
23:22 / 23:23≈ on time ≈ +2 min
23:26 / 23:27≈ on time ≈ +2 min
23:30≈ on time ≈ +2 min
23:34≈ on time ≈ +2 min
23:39 / 23:41≈ on time ≈ +2 min
23:47 / 23:48≈ on time ≈ +2 min
23:53≈ on time ≈ +2 min
23:57≈ on time ≈ +2 min
00:03on 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
Sun 15 NovNowogard 00:07+3 min+3 min
Thu 12 NovNowogard 00:040 min—
Wed 11 NovNowogard 00:040 min—
Mon 9 NovNowogard 00:040 min—
Sun 8 NovNowogard 00:040 min—
Thu 5 NovNowogard 00:040 min—
Wed 4 NovNowogard 00:04No data—
Tue 3 NovNowogard 00:040 min—
Mon 2 NovNowogard 00:040 min—
Sun 1 NovNowogard 00:09+6 min+6 min
Thu 29 OctNowogard 00:040 min—
Wed 28 OctNowogard 00:040 min—
Tue 27 OctNowogard 00:06+2 min+2 min
Mon 26 OctNowogard 00:050 min—
Sun 25 OctNowogard 00:04No data—
Thu 22 OctNowogard 23:44No data—
Wed 21 OctNowogard 23:44No data—
Tue 20 OctNowogard 23:44No data—
Mon 19 OctNowogard 23:44No data—
Sun 18 OctNowogard 23:450 min—
Thu 15 OctNowogard 23:450 min—
Wed 14 OctNowogard 23:450 min—
Tue 13 OctNowogard 23:440 min—
Mon 12 OctNowogard 23:440 min—
Sun 11 OctNowogard 23:440 min—
Thu 8 OctNowogard 23:440 min—
Wed 7 OctNowogard 23:450 min—
Tue 6 OctNowogard 23:440 min—
Mon 5 OctNowogard 23:43−1 min—
Sun 4 OctNowogard 23:440 min—