REG 88670 Gryfice – Koszalin

View line REG

Gryfice 05:10 → Koszalin 06:55 Mon, Tue, Wed, Thu, Fri 1 h 45 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Koszalin at 06:57 +2 min

  1. Gryfice05:10
  2. Trzebiatów05:27
  3. Głowaczewo05:46
  4. Kołobrzeg Stadion05:58
  5. Ustronie Morskie06:25
  6. Słowienkowo06:38
  7. Koszalin06:55

Next service: Monday 05:10 from Gryfice · Mon 23 Nov

Next departure 05:10 Monday · Gryfice
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 12 full · 0 partial · 9 no data
On-time · 90 days
88%
28/32 runs under 3 min
RT coverage: 32 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Koszalin, 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 19 Oct Max en route +42 min · last fix heading to Koszalin +40 min
  • Fri 11 Sept Max en route +9 min · last fix heading to Mścice +9 min
  • Fri 18 Sept Max en route +7 min · last fix heading to Koszalin +7 min
  • Thu 19 Nov Max en route +3 min · last fix heading to Koszalin +3 min

Distribution · 90 days

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

  • Early 9% · 3
  • On time 78% · 25
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 89% M n=9
  • 100% T n=5
  • 100% W n=5
  • 75% T n=4
  • 78% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 32 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
05:10on time on time
05:15 / 05:16≈ on time ≈ +2 min
05:21 / 05:22≈ on time ≈ +2 min
05:27 / 05:33≈ on time ≈ +2 min
05:38 / 05:39≈ on time ≈ +2 min
05:42 / 05:43≈ on time ≈ +2 min
05:46 / 05:47≈ on time ≈ +2 min
05:50≈ on time ≈ +2 min
05:54 / 05:55≈ on time ≈ +2 min
05:58≈ on time ≈ +2 min
06:02 / 06:14≈ on time ≈ +2 min
06:17≈ on time ≈ +2 min
06:25 / 06:26≈ on time ≈ +2 min
06:31≈ on time ≈ +2 min
06:35≈ on time ≈ +2 min
06:38≈ on time ≈ +2 min
06:41 / 06:42≈ on time ≈ +3 min
06:47≈ on time ≈ +3 min
06:55on time +3 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
Fri 20 NovKoszalin 06:59+2 min+2 min
Thu 19 NovKoszalin 06:59+3 min+3 min
Wed 18 NovKoszalin 06:54−1 min—
Tue 17 NovKoszalin 06:540 min—
Mon 16 NovKoszalin 06:540 min—
Fri 13 NovKoszalin 06:540 min—
Thu 12 NovKoszalin 06:54No data—
Tue 10 NovKoszalin 06:54No data—
Mon 9 NovKoszalin 06:58+2 min+2 min
Fri 6 NovKoszalin 06:540 min—
Thu 5 NovKoszalin 06:54No data—
Wed 4 NovKoszalin 06:54No data—
Tue 3 NovKoszalin 06:54No data—
Mon 2 NovKoszalin 06:540 min—
Fri 30 OctKoszalin 06:560 min—
Thu 29 OctKoszalin 06:56No data—
Wed 28 OctKoszalin 06:560 min—
Tue 27 OctKoszalin 06:56No data—
Mon 26 OctKoszalin 06:560 min—
Fri 23 OctKoszalin 06:58No data—
Thu 22 OctKoszalin 06:58No data—
Wed 21 OctKoszalin 06:58No data—
Tue 20 OctKoszalin 06:58No data—
Mon 19 OctKoszalin 07:38+40 min+42 min
Fri 16 OctKoszalin 06:580 min—
Thu 15 OctKoszalin 06:580 min—
Wed 14 OctKoszalin 06:58No data—
Tue 13 OctKoszalin 06:57−1 min—
Mon 12 OctKoszalin 06:590 min—
Fri 9 OctKoszalin 06:56−2 min—