REG 80289 Koszalin – Świdwin

View line REG

Koszalin 06:03 → Świdwin 07:10 Mon, Tue, Wed, Thu, Fri 1 h 07 min · 9 stops PolRegio

It does not run today

Last recorded run: Friday 13 November +3 min

Next service: tomorrow 06:03 from Koszalin · Mon 16 Nov

Next departure 06:03 tomorrow · Koszalin
On-time · 30 days
60%
9/15 runs under 3 min
RT coverage: 15 full · 0 partial · 4 no data
On-time · 90 days
72%
21/29 runs under 3 min
RT coverage: 29 full · 0 partial · 15 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Świdwin, 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 13 Oct Max en route +9 min · last fix heading to Świdwin +9 min
  • Mon 12 Oct Max en route +9 min · last fix heading to Świdwin +9 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Świdwin +4 min
  • Thu 5 Nov Max en route +4 min · last fix heading to Świdwin +4 min
  • Mon 19 Oct Max en route +4 min · last fix heading to Świdwin +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 72% · 21
  • 3–10 min 28% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 60% T n=5
  • 100% W n=5
  • 67% T n=6
  • 83% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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
06:03+1 min +3 min
06:09 / 06:10≈ +1 min ≈ +3 min
06:13 / 06:18≈ +1 min ≈ +3 min
06:21 / 06:22≈ +1 min ≈ +3 min
06:27 / 06:44≈ +1 min ≈ +3 min
06:49 / 06:54≈ +1 min ≈ +3 min
06:59≈ +1 min ≈ +3 min
07:04≈ +1 min ≈ +4 min
07:10+1 min +4 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 13 NovŚwidwin 07:14+3 min+3 min
Thu 12 NovŚwidwin 07:14+4 min+4 min
Tue 10 NovŚwidwin 07:14+3 min+3 min
Mon 9 NovŚwidwin 07:14+3 min+3 min
Fri 6 NovŚwidwin 07:13+1 min+1 min
Thu 5 NovŚwidwin 07:14+4 min+4 min
Wed 4 NovŚwidwin 07:090 min—
Tue 3 NovŚwidwin 07:090 min—
Mon 2 NovŚwidwin 07:090 min—
Fri 30 OctŚwidwin 07:13+2 min+2 min
Thu 29 OctŚwidwin 07:110 min—
Wed 28 OctŚwidwin 07:12+1 min+1 min
Tue 27 OctŚwidwin 07:110 min—
Mon 26 OctŚwidwin 07:110 min—
Fri 23 OctŚwidwin 07:11No data—
Thu 22 OctŚwidwin 07:11No data—
Wed 21 OctŚwidwin 07:11No data—
Tue 20 OctŚwidwin 07:11No data—
Mon 19 OctŚwidwin 07:15+4 min+4 min
Fri 16 OctŚwidwin 07:110 min—
Thu 15 OctŚwidwin 07:110 min—
Wed 14 OctŚwidwin 07:110 min—
Tue 13 OctŚwidwin 07:20+9 min+9 min
Mon 12 OctŚwidwin 07:21+9 min+9 min
Fri 9 OctŚwidwin 07:13+2 min+2 min
Thu 8 OctŚwidwin 07:12+1 min+1 min
Wed 7 OctŚwidwin 07:12+1 min+1 min
Tue 6 OctŚwidwin 07:13+1 min+1 min
Mon 5 OctŚwidwin 07:13+1 min+1 min
Fri 2 OctŚwidwin 07:09No data—