REG 70349 Zbąszynek – Rzepin

View line REG

Zbąszynek 13:40 → Rzepin 14:37 Mon, Tue, Thu, Fri, Sat 0 h 57 min · 11 stops PolRegio

Running now · updated 14:18

Between Drzewce and Torzym 0 min

Estimated arrival at Rzepin 14:37 · 104 km/h

  1. Zbąszynek13:40
  2. Kupienino13:52
  3. Świebodzin13:56
  4. Mostki14:04
  5. Drzewce14:17
  6. Torzym14:23
  7. Rzepin14:37

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

On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 19 full · 1 partial · 6 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 29 full · 1 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sat 31 Oct Max en route +6 min · last fix heading to Rzepin +6 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Rzepin +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 90% · 27
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 75% W n=4
  • 100% T n=5
  • 100% F n=5
  • 83% S n=6
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (11 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
13:40on time +1 minPassed
13:47 / 13:48≈ on time ≈ +1 minPassed
13:52≈ on time ≈ +1 minPassed
13:56≈ on time ≈ +1 minPassed
14:00≈ on time ≈ +1 minPassed
14:04≈ on time ≈ +1 minPassed
14:11 / 14:12≈ on time ≈ +1 minPassed
14:17≈ on time ≈ +1 minPassed
14:23 / 14:24≈ on time ≈ +1 minNext
14:29≈ on time ≈ +1 min
14:37on time +1 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 NovDrzewce 14:14Partial coverage0 min—
Mon 9 NovRzepin 14:380 min—
Sat 7 NovRzepin 14:390 min—
Fri 6 NovRzepin 14:380 min—
Thu 5 NovRzepin 14:380 min—
Wed 4 NovRzepin 14:39+3 min+3 min
Tue 3 NovRzepin 14:380 min—
Mon 2 NovRzepin 14:380 min—
Sat 31 OctRzepin 14:44+6 min+6 min
Fri 30 OctRzepin 14:380 min—
Thu 29 OctRzepin 14:36−2 min—
Wed 28 OctRzepin 14:380 min—
Tue 27 OctRzepin 14:37−1 min—
Mon 26 OctRzepin 14:380 min—
Sat 24 OctRzepin 14:34No data—
Fri 23 OctRzepin 14:34No data—
Thu 22 OctRzepin 14:34No data—
Wed 21 OctRzepin 14:35No data—
Tue 20 OctRzepin 14:34No data—
Mon 19 OctRzepin 14:34No data—
Sat 17 OctRzepin 14:330 min—
Fri 16 OctRzepin 14:340 min—
Thu 15 OctRzepin 14:35+1 min+1 min
Wed 14 OctRzepin 14:340 min—
Tue 13 OctRzepin 14:34−1 min—
Mon 12 OctRzepin 14:340 min+1 min
Sat 10 OctRzepin 14:350 min—
Fri 9 OctRzepin 14:36+2 min+2 min
Thu 8 OctRzepin 14:340 min—
Wed 7 OctRzepin 14:340 min—