REG 5161 Küstrien-Kietz – Kostrzyn

View line REG

Küstrien-Kietz 11:47 → Kostrzyn 11:52 Daily 0 h 05 min · 2 stops PolRegio

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 11:47 from Küstrien-Kietz · Wed 11 Nov

Next departure 11:47 today · Küstrien-Kietz
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 22 full · 0 partial · 6 no data
On-time · 90 days
68%
26/38 runs under 3 min
RT coverage: 38 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+17min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Kostrzyn, 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 +37 min · last fix heading to Obersdorf +37 min
  • Wed 14 Oct Max en route +26 min · last fix heading to Kostrzyn +26 min
  • Thu 29 Oct Max en route +19 min · last fix heading to Kostrzyn +19 min
  • Tue 15 Sept Max en route +17 min · last fix heading to Werbig +17 min
  • Sun 13 Sept Max en route +17 min · last fix heading to Werbig +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 26
  • 3–10 min 18% · 7
  • 10–30 min 11% · 4
  • 30+ min 3% · 1

On-time by weekday

  • 63% M n=8
  • 83% T n=6
  • 75% W n=4
  • 75% T n=4
  • 100% F n=4
  • 60% S n=5
  • 43% S n=7

Stops and timetable

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

Last 90 days, 38 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:47on time +17 min
11:52on time +17 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
Tue 10 NovKostrzyn 11:530 min—
Mon 9 NovKostrzyn 11:540 min—
Sun 8 NovKostrzyn 11:540 min—
Sat 7 NovKostrzyn 11:530 min—
Fri 6 NovKostrzyn 11:530 min—
Thu 5 NovKostrzyn 11:530 min—
Wed 4 NovKostrzyn 11:530 min—
Tue 3 NovKostrzyn 11:530 min—
Mon 2 NovKostrzyn 11:53No data—
Sun 1 NovKostrzyn 11:58+5 min+5 min
Sat 31 OctKostrzyn 11:530 min—
Fri 30 OctKostrzyn 11:530 min—
Thu 29 OctKostrzyn 12:12+19 min+19 min
Wed 28 OctKostrzyn 11:530 min—
Tue 27 OctKostrzyn 11:530 min—
Mon 26 OctKostrzyn 11:530 min—
Sun 25 OctKostrzyn 11:53No data—
Sat 24 OctKostrzyn 11:53No data—
Thu 22 OctKostrzyn 11:53No data—
Wed 21 OctKostrzyn 11:53No data—
Tue 20 OctKostrzyn 11:53No data—
Mon 19 OctKostrzyn 11:530 min—
Sun 18 OctKostrzyn 11:57+4 min+4 min
Sat 17 OctKostrzyn 11:57+4 min+4 min
Fri 16 OctKostrzyn 11:530 min—
Thu 15 OctKostrzyn 11:530 min—
Wed 14 OctKostrzyn 12:20+26 min+26 min
Tue 13 OctKostrzyn 11:530 min—
Mon 12 OctKostrzyn 11:530 min—
Sun 11 OctKostrzyn 11:530 min—