REG 5174 Kostrzyn – Küstrien-Kietz

View line REG

Kostrzyn 16:05 → Küstrien-Kietz 16:10 Daily 0 h 05 min · 2 stops PolRegio

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 16:05 from Kostrzyn · Fri 13 Nov

Next departure 16:05 today · Kostrzyn
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
78%
35/45 runs under 3 min
RT coverage: 45 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Küstrien-Kietz, 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 14 Sept Max en route +28 min · last fix heading to Müncheberg (Mark) +28 min
  • Sun 13 Sept Max en route +28 min · last fix heading to Müncheberg (Mark) +28 min
  • Mon 31 Aug Max en route +9 min · last fix heading to Kostrzyn +9 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Rehfelde +7 min
  • Mon 12 Oct Max en route +7 min · last fix heading to Rehfelde +7 min

Distribution · 90 days

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

  • Early 13% · 6
  • On time 64% · 29
  • 3–10 min 18% · 8
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 71% T n=7
  • 100% W n=6
  • 100% T n=6
  • 83% F n=6
  • 83% S n=6
  • 50% S n=6

Stops and timetable

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

Last 90 days, 45 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
16:05on time +7 min
16:10on time +7 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 12 NovKüstrien-Kietz 16:090 min—
Wed 11 NovKüstrien-Kietz 16:090 min—
Tue 10 NovKüstrien-Kietz 16:090 min—
Mon 9 NovKüstrien-Kietz 16:090 min—
Sun 8 NovKüstrien-Kietz 16:090 min—
Sat 7 NovKüstrien-Kietz 16:090 min—
Fri 6 NovKüstrien-Kietz 16:090 min—
Thu 5 NovKüstrien-Kietz 16:090 min—
Wed 4 NovKüstrien-Kietz 16:090 min—
Tue 3 NovKüstrien-Kietz 16:100 min—
Mon 2 NovKüstrien-Kietz 16:090 min—
Sun 1 NovKüstrien-Kietz 16:16+5 min+5 min
Sat 31 OctKüstrien-Kietz 16:120 min—
Fri 30 OctKüstrien-Kietz 16:110 min—
Thu 29 OctKüstrien-Kietz 16:110 min—
Wed 28 OctKüstrien-Kietz 16:110 min—
Tue 27 OctKüstrien-Kietz 16:110 min—
Mon 26 OctKüstrien-Kietz 16:120 min—
Sun 25 OctKüstrien-Kietz 16:11No data—
Sat 24 OctRehfelde 16:48−5 min—
Fri 23 OctRehfelde 16:49−5 min—
Thu 22 OctRehfelde 16:49−5 min—
Wed 21 OctRehfelde 16:49−5 min—
Tue 20 OctRehfelde 16:48−5 min—
Mon 19 OctRehfelde 16:49−5 min—
Sun 18 OctRehfelde 16:540 min—
Sat 17 OctRehfelde 16:540 min—
Fri 16 OctRehfelde 16:530 min—
Thu 15 OctRehfelde 16:530 min—
Wed 14 OctRehfelde 16:530 min—