REG 5623 Cottbus Hauptbahnhof – Żagań

View line REG

Cottbus Hauptbahnhof 18:07 → Żagań 19:18 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 11 stops PolRegio

✓ Today’s run finished

Today it reached Żagań at 19:18 0 min

  1. Cottbus Hauptbahnhof18:07
  2. Klinge18:24
  3. Forst (Lausitz)18:31
  4. Tuplice18:45
  5. Lipinki Łużyckie18:56
  6. Sieniawa Żarska19:00
  7. Żagań19:18

Next service: tomorrow 18:07 from Cottbus Hauptbahnhof · Fri 20 Nov

Next departure 18:07 tomorrow · Cottbus Hauptbahnhof
On-time · 30 days
83%
15/18 runs under 3 min
RT coverage: 18 full · 0 partial · 3 no data
On-time · 90 days
65%
24/37 runs under 3 min
RT coverage: 37 full · 0 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+20min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Żagań, in minutes. One bar per run.

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

Worst days

  • Wed 30 Sept Max en route +24 min · last fix heading to Żagań +24 min
  • Tue 1 Sept Max en route +24 min · last fix heading to Lipinki Łużyckie +24 min
  • Tue 29 Sept Max en route +23 min · last fix heading to Lipinki Łużyckie +23 min
  • Mon 31 Aug Max en route +21 min · last fix heading to Lipinki Łużyckie +21 min
  • Wed 9 Sept Max en route +19 min · last fix heading to Sieniawa Żarska +19 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 24
  • 3–10 min 16% · 6
  • 10–30 min 19% · 7
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 56% T n=9
  • 71% W n=7
  • 71% T n=7
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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
18:07on time +18 min
18:16≈ on time ≈ +19 min
18:24≈ on time ≈ +19 min
18:31≈ on time ≈ +19 min
18:35≈ on time ≈ +19 min
18:45 / 18:46≈ on time ≈ +20 min
18:50≈ on time ≈ +20 min
18:56≈ on time ≈ +20 min
19:00≈ on time ≈ +20 min
19:06 / 19:07≈ on time ≈ +20 min
19:18on time +20 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 19 NovŻagań 19:190 min—
Wed 18 NovŻagań 19:190 min—
Tue 17 NovŻagań 19:190 min—
Mon 16 NovŻagań 19:190 min—
Fri 13 NovŻagań 19:190 min—
Thu 12 NovŻagań 19:190 min+16 min
Tue 10 NovŻagań 19:190 min—
Mon 9 NovŻagań 19:190 min—
Fri 6 NovŻagań 19:190 min—
Thu 5 NovŻagań 19:190 min—
Wed 4 NovŻagań 19:190 min—
Tue 3 NovŻagań 19:20+1 min+1 min
Mon 2 NovŻagań 19:19+1 min+16 min
Fri 30 OctŻagań 19:190 min—
Thu 29 OctŻagań 19:29+10 min+10 min
Wed 28 OctŻagań 19:190 min—
Tue 27 OctŻagań 19:23+4 min+4 min
Mon 26 OctŻagań 19:24+4 min+16 min
Fri 23 OctŻagań 19:20No data—
Thu 22 OctŻagań 19:19No data—
Wed 21 OctŻagań 19:19No data—
Tue 20 OctŻagań 19:19No data—
Mon 19 OctŻagań 19:19No data—
Fri 16 OctŻagań 19:22+2 min+2 min
Thu 15 OctŻagań 19:190 min—
Wed 14 OctŻagań 19:190 min—
Tue 13 OctŻagań 19:190 min—
Mon 12 OctŻagań 19:190 min+16 min
Fri 9 OctŻagań 19:22+3 min+3 min
Thu 8 OctŻagań 19:190 min—