REG 70355 Zbąszynek – Rzepin

View line REG

Zbąszynek 18:30 → Rzepin 19:27 Daily 0 h 57 min · 11 stops PolRegio

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 18:30 from Zbąszynek · Mon 9 Nov

Next departure 18:30 today · Zbąszynek
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 31 full · 0 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Thu 15 Oct Max en route +38 min · last fix heading to Rzepin +37 min
  • Sun 1 Nov Max en route +7 min · last fix heading to Rzepin +7 min
  • Fri 9 Oct Max en route +5 min · last fix heading to Rzepin +5 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Rzepin +3 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 81% · 25
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=5
  • 75% T n=4
  • 80% F n=5
  • 75% S n=4
  • 80% S n=5

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
18:30on time +1 min
18:37 / 18:38≈ on time ≈ +3 min
18:42≈ on time ≈ +3 min
18:46≈ on time ≈ +3 min
18:50≈ on time ≈ +3 min
18:54≈ on time ≈ +3 min
19:01 / 19:02≈ on time ≈ +3 min
19:07≈ on time ≈ +3 min
19:13 / 19:14≈ on time ≈ +3 min
19:19≈ on time ≈ +3 min
19:27on time +3 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
Sun 8 NovRzepin 19:280 min—
Sat 7 NovRzepin 19:29+3 min+3 min
Fri 6 NovRzepin 19:280 min—
Thu 5 NovRzepin 19:25−2 min—
Wed 4 NovRzepin 19:280 min—
Tue 3 NovRzepin 19:30+1 min+1 min
Mon 2 NovRzepin 19:29+2 min+2 min
Sun 1 NovRzepin 19:34+7 min+7 min
Sat 31 OctRzepin 19:290 min—
Fri 30 OctRzepin 19:27−1 min—
Thu 29 OctRzepin 19:280 min—
Wed 28 OctRzepin 19:280 min—
Tue 27 OctRzepin 19:280 min—
Mon 26 OctRzepin 19:290 min—
Sun 25 OctRzepin 19:28No data—
Sat 24 OctRzepin 19:29No data—
Fri 23 OctRzepin 19:29No data—
Thu 22 OctRzepin 19:28No data—
Wed 21 OctRzepin 19:28No data—
Tue 20 OctRzepin 19:28No data—
Mon 19 OctRzepin 19:28No data—
Sun 18 OctRzepin 19:280 min—
Sat 17 OctRzepin 19:280 min—
Fri 16 OctRzepin 19:30+1 min+1 min
Thu 15 OctRzepin 20:06+37 min+38 min
Wed 14 OctRzepin 19:280 min—
Tue 13 OctRzepin 19:280 min—
Mon 12 OctRzepin 19:29+1 min+1 min
Sun 11 OctRzepin 19:27−1 min—
Sat 10 OctRzepin 19:29+1 min+1 min