KD Sprinter 60161 Wrocław Główny – Rawicz

View line KD Sprinter

Wrocław Główny 05:32 → Rawicz 06:07 Daily 0 h 35 min · 5 stops Koleje Dolnośląskie

It has not run yet today

Last recorded run: Thursday 5 November −2 min

Next service: today 05:32 from Wrocław Główny · Fri 6 Nov

Next departure 05:32 today · Wrocław Główny
On-time · 30 days
87%
20/23 runs under 3 min
RT coverage: 23 full · 0 partial · 6 no data
On-time · 90 days
85%
50/59 runs under 3 min
RT coverage: 59 full · 0 partial · 9 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Rawicz, 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 12 Sept Max en route +28 min · last fix heading to Oborniki Śląskie +28 min
  • Sun 13 Sept Max en route +17 min · last fix heading to Żmigród +17 min
  • Sun 1 Nov Max en route +13 min · last fix heading to Rawicz +13 min
  • Wed 16 Sept Max en route +8 min · last fix heading to Rawicz +8 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Rawicz +5 min

Distribution · 90 days

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

  • Early 51% · 30
  • On time 34% · 20
  • 3–10 min 10% · 6
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 89% T n=9
  • 78% W n=9
  • 100% T n=9
  • 88% F n=8
  • 75% S n=8
  • 71% S n=7

Stops and timetable

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

Last 90 days, 59 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:322 min early +3 min
05:36 / 05:37≈ 2 min early ≈ +3 min
05:47 / 05:48≈ 2 min early ≈ +3 min
05:58≈ 2 min early ≈ +3 min
06:072 min early +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
Thu 5 NovRawicz 06:04−2 min—
Wed 4 NovRawicz 06:04−2 min—
Tue 3 NovRawicz 06:09+2 min+2 min
Mon 2 NovRawicz 06:07−1 min—
Sun 1 NovRawicz 06:22+13 min+13 min
Sat 31 OctRawicz 06:13+5 min+5 min
Fri 30 OctRawicz 06:13+5 min+5 min
Thu 29 OctRawicz 06:07−1 min—
Wed 28 OctRawicz 06:080 min—
Tue 27 OctRawicz 06:06−2 min—
Mon 26 OctRawicz 06:07−1 min—
Sun 25 OctRawicz 06:08No data—
Sat 24 OctRawicz 06:08No data—
Fri 23 OctRawicz 06:08No data—
Thu 22 OctRawicz 06:08No data—
Wed 21 OctRawicz 06:08No data—
Tue 20 OctRawicz 06:08No data—
Mon 19 OctRawicz 06:09+1 min+1 min
Sun 18 OctRawicz 06:090 min—
Sat 17 OctRawicz 06:080 min—
Fri 16 OctRawicz 06:07−2 min—
Thu 15 OctRawicz 06:06−2 min—
Wed 14 OctRawicz 06:06−2 min—
Tue 13 OctRawicz 06:06−2 min—
Mon 12 OctRawicz 06:07−2 min—
Sun 11 OctRawicz 06:080 min—
Sat 10 OctRawicz 06:080 min—
Fri 9 OctRawicz 06:06−2 min—
Thu 8 OctRawicz 06:07−2 min—
Wed 7 OctRawicz 06:11+3 min+3 min