REG 70725 Zielona Góra Główna – Rzepin

View line REG

Zielona Góra Główna 22:59 → Rzepin 23:59 Daily 1 h 00 min · 13 stops PolRegio

Running now · updated 00:04

Position estimated from the timetable

Between Rzepin Miasto and Rzepin +33 min

Estimated arrival at Rzepin 00:32 23:59

  1. Zielona Góra Główna22:59
  2. Czerwieńsk23:10
  3. Będów23:19
  4. Bytnica23:29
  5. Pliszka23:39
  6. Rzepin Miasto23:57
  7. Rzepin23:59

Today it is running worse than usual: typical arrival delay is 0 min; 80% of the last 10 runs arrived on time.

On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 19 no data
On-time · 90 days
77%
23/30 runs under 3 min
RT coverage: 30 full · 0 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +13 min

Last 30 days

Arrival delay at Rzepin, 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 16 Nov Max en route +36 min · last fix heading to Rzepin +36 min
  • Mon 31 Aug Max en route +31 min · last fix heading to Bytnica +31 min
  • Mon 26 Oct Max en route +10 min · last fix heading to Rzepin +10 min
  • Fri 25 Sept Max en route +8 min · last fix heading to Jerzmanice Lubuskie +8 min
  • Mon 12 Oct Max en route +6 min · last fix heading to Rzepin +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 23
  • 3–10 min 13% · 4
  • 10–30 min 3% · 1
  • 30+ min 7% · 2

On-time by weekday

  • 50% M n=8
  • 100% T n=3
  • 100% W n=2
  • 100% T n=3
  • 75% F n=4
  • 83% S n=6
  • 75% S n=4

Stops and timetable

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

Last 90 days, 30 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 10Today
22:59on time on timePassed
23:05≈ on time ≈ +3 minPassed
23:10 / 23:11≈ on time ≈ +3 minPassed
23:15 / 23:16≈ on time ≈ +4 minPassed
23:19≈ on time ≈ +4 minPassed
23:22≈ on time ≈ +4 minPassed
23:29≈ on time ≈ +5 minPassed
23:33 / 23:34≈ on time ≈ +6 minPassed
23:39 / 23:40≈ on time ≈ +7 minPassed
23:45≈ on time ≈ +8 minPassed
23:52≈ on time ≈ +8 minPassed
23:57≈ on time ≈ +8 minPassed
23:59on time +8 minNext

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 20 NovRzepin 23:590 min—
Thu 19 NovRzepin 23:590 min—
Wed 18 NovRzepin 23:59No data—
Tue 17 NovRzepin 23:59No data—
Mon 16 NovRzepin 00:34+36 min+36 min
Sun 15 NovRzepin 23:59+2 min+2 min
Sat 14 NovRzepin 23:590 min—
Fri 13 NovRzepin 23:590 min—
Thu 12 NovRzepin 23:59No data—
Wed 11 NovRzepin 23:59No data—
Tue 10 NovRzepin 00:00No data—
Mon 9 NovRzepin 23:590 min—
Sun 8 NovRzepin 23:59No data—
Sat 7 NovRzepin 23:59No data—
Fri 6 NovRzepin 23:59No data—
Thu 5 NovRzepin 23:59No data—
Wed 4 NovRzepin 23:59No data—
Tue 3 NovRzepin 23:59No data—
Mon 2 NovRzepin 23:590 min—
Sun 1 NovRzepin 23:59No data—
Sat 31 OctRzepin 00:02+1 min+1 min
Fri 30 OctRzepin 00:00No data—
Thu 29 OctRzepin 00:00No data—
Wed 28 OctRzepin 00:00No data—
Tue 27 OctRzepin 00:00No data—
Mon 26 OctRzepin 00:11+10 min+10 min
Sun 25 OctRzepin 00:00No data—
Sat 24 OctRzepin 00:01No data—
Fri 23 OctRzepin 00:01No data—
Thu 22 OctRzepin 00:01No data—