KW 70293 Rawicz – Leszno

View line KW

Rawicz 05:10 → Leszno 05:35 Daily 0 h 25 min · 5 stops Koleje Wielkopolskie

It has not run yet today

Last recorded run: Tuesday 10 November −1 min

Next service: today 05:10 from Rawicz · Wed 11 Nov

Next departure 05:10 today · Rawicz
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
On-time · 90 days
98%
55/56 runs under 3 min
RT coverage: 56 full · 0 partial · 16 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −2 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Leszno, in minutes. One bar per run.

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

Worst days

  • Sun 1 Nov Max en route +12 min · last fix heading to Leszno +12 min

Distribution · 90 days

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

  • Early 63% · 35
  • On time 36% · 20
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=9
  • 100% W n=7
  • 100% T n=9
  • 100% F n=8
  • 100% S n=7
  • 86% S n=7

Stops and timetable

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

Last 90 days, 56 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
05:102 min early +1 min
05:17 / 05:18≈ 2 min early ≈ +1 min
05:22 / 05:23≈ 2 min early ≈ +1 min
05:26≈ 2 min early ≈ +1 min
05:352 min early +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 NovLeszno 05:34−1 min—
Mon 9 NovLeszno 05:34−2 min—
Sun 8 NovLeszno 05:340 min—
Sat 7 NovLeszno 05:340 min—
Fri 6 NovLeszno 05:38+2 min+2 min
Thu 5 NovLeszno 05:34−2 min—
Wed 4 NovLeszno 05:33−3 min—
Tue 3 NovLeszno 05:33−3 min—
Mon 2 NovLeszno 05:33−3 min—
Sun 1 NovLeszno 05:49+12 min+12 min
Sat 31 OctLeszno 05:34−2 min—
Fri 30 OctLeszno 05:34−2 min—
Thu 29 OctLeszno 05:34−2 min—
Wed 28 OctLeszno 05:37+1 min+1 min
Tue 27 OctLeszno 05:370 min—
Mon 26 OctLeszno 05:38+2 min+2 min
Sun 25 OctLeszno 05:36No data—
Sat 24 OctLeszno 05:36No data—
Fri 23 OctLeszno 05:36No data—
Thu 22 OctLeszno 05:36No data—
Wed 21 OctLeszno 05:36No data—
Tue 20 OctLeszno 05:36No data—
Mon 19 OctLeszno 05:34−2 min—
Sun 18 OctLeszno 05:33−3 min—
Sat 17 OctLeszno 05:33−3 min—
Fri 16 OctLeszno 05:35−2 min—
Thu 15 OctLeszno 05:37+1 min+1 min
Wed 14 OctLeszno 05:34−2 min—
Tue 13 OctLeszno 05:33−3 min—
Mon 12 OctLeszno 05:33−3 min—