REG 5618 Żagań – Cottbus Hauptbahnhof

View line REG

Żagań 10:37 → Cottbus Hauptbahnhof 11:49 Mon, Tue, Wed, Thu, Fri 1 h 12 min · 11 stops PolRegio

✓ Today’s run finished

Today it reached Cottbus Hauptbahnhof at 11:49 0 min

  1. Żagań10:37
  2. Sieniawa Żarska11:00
  3. Lipinki Łużyckie11:04
  4. Tuplice11:15
  5. Forst (Lausitz)11:31
  6. Klinge11:37
  7. Cottbus Hauptbahnhof11:49

Next service: tomorrow 10:37 from Żagań · Fri 13 Nov

Next departure 10:37 tomorrow · Żagań
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Cottbus Hauptbahnhof, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 16% · 5
  • On time 84% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 31 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
10:37on time on time
10:48 / 10:56≈ on time ≈ on time
11:00≈ on time ≈ on time
11:04≈ on time ≈ on time
11:10 / 11:11≈ on time ≈ on time
11:15 / 11:16≈ on time ≈ on time
11:26 / 11:27≈ on time ≈ on time
11:31≈ on time ≈ on time
11:37≈ on time ≈ on time
11:45≈ on time ≈ on time
11:49on time on time

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 NovCottbus Hauptbahnhof 11:490 min—
Tue 10 NovCottbus Hauptbahnhof 11:490 min—
Mon 9 NovCottbus Hauptbahnhof 11:490 min—
Fri 6 NovCottbus Hauptbahnhof 11:490 min—
Thu 5 NovCottbus Hauptbahnhof 11:490 min—
Wed 4 NovCottbus Hauptbahnhof 11:490 min—
Tue 3 NovCottbus Hauptbahnhof 11:490 min—
Mon 2 NovCottbus Hauptbahnhof 11:490 min—
Fri 30 OctCottbus Hauptbahnhof 11:500 min—
Thu 29 OctCottbus Hauptbahnhof 11:500 min—
Wed 28 OctCottbus Hauptbahnhof 11:500 min—
Tue 27 OctCottbus Hauptbahnhof 11:500 min—
Mon 26 OctCottbus Hauptbahnhof 11:500 min—
Fri 23 OctCottbus Hauptbahnhof 11:44−6 min—
Thu 22 OctCottbus Hauptbahnhof 11:44−6 min—
Wed 21 OctCottbus Hauptbahnhof 11:44−6 min—
Tue 20 OctCottbus Hauptbahnhof 11:44−6 min—
Mon 19 OctCottbus Hauptbahnhof 11:44−6 min—
Fri 16 OctCottbus Hauptbahnhof 11:500 min—
Thu 15 OctCottbus Hauptbahnhof 11:500 min—
Wed 14 OctCottbus Hauptbahnhof 11:510 min—
Tue 13 OctCottbus Hauptbahnhof 11:500 min—
Mon 12 OctCottbus Hauptbahnhof 11:500 min—
Fri 9 OctCottbus Hauptbahnhof 11:510 min—
Thu 8 OctCottbus Hauptbahnhof 11:500 min—
Wed 7 OctCottbus Hauptbahnhof 11:500 min—
Tue 6 OctCottbus Hauptbahnhof 11:500 min—
Mon 5 OctCottbus Hauptbahnhof 11:500 min—
Fri 2 OctCottbus Hauptbahnhof 11:48No data—
Thu 1 OctCottbus Hauptbahnhof 11:48No data—