KW 70231 Kalisz – Krotoszyn

View line KW

Kalisz 15:03 → Krotoszyn 15:55 Daily 0 h 52 min · 12 stops Koleje Wielkopolskie

It has not run yet today

Last recorded run: Thursday 5 November +3 min

Next service: today 15:03 from Kalisz · Fri 6 Nov

Next departure 15:03 today · Kalisz
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 14 no data
On-time · 90 days
84%
16/19 runs under 3 min
RT coverage: 19 full · 0 partial · 27 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: +2 min

Last 30 days

Arrival delay at Krotoszyn, 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 +11 min · last fix heading to Krotoszyn +11 min
  • Fri 2 Oct Max en route +4 min · last fix heading to Biadki +4 min
  • Thu 5 Nov Max en route +3 min · last fix heading to Krotoszyn +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 16
  • 3–10 min 11% · 2
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=3
  • 67% T n=3
  • 50% F n=2
  • 100% S n=1
  • 50% S n=2

Stops and timetable

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

Last 90 days, 19 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
15:03on time +2 min
15:05 / 15:06≈ on time ≈ +2 min
15:09≈ on time ≈ +2 min
15:13≈ on time ≈ +3 min
15:17 / 15:18≈ on time ≈ +3 min
15:22 / 15:26≈ on time ≈ +3 min
15:31 / 15:32≈ on time ≈ +3 min
15:35 / 15:36≈ on time ≈ +3 min
15:39≈ on time ≈ +3 min
15:42 / 15:43≈ on time ≈ +3 min
15:46 / 15:47≈ on time ≈ +3 min
15:55on 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
Thu 5 NovKrotoszyn 15:59+3 min+3 min
Wed 4 NovKrotoszyn 15:540 min—
Tue 3 NovKrotoszyn 15:550 min—
Mon 2 NovKrotoszyn 15:540 min—
Sun 1 NovKrotoszyn 16:07+11 min+11 min
Sat 31 OctKrotoszyn 15:570 min—
Fri 30 OctKrotoszyn 15:560 min—
Thu 29 OctKrotoszyn 15:560 min—
Wed 28 OctKrotoszyn 15:560 min—
Tue 27 OctKrotoszyn 15:560 min—
Mon 26 OctKrotoszyn 15:570 min—
Sun 25 OctKrotoszyn 15:56No data—
Sat 24 OctKrotoszyn 15:56No data—
Fri 23 OctKrotoszyn 15:56No data—
Thu 22 OctKrotoszyn 15:56No data—
Wed 21 OctKrotoszyn 15:57No data—
Tue 20 OctKrotoszyn 15:56No data—
Mon 19 OctKrotoszyn 15:57No data—
Sun 18 OctKrotoszyn 15:560 min—
Sat 17 OctGorzupia 15:50No data—
Fri 16 OctGorzupia 15:23No data—
Thu 15 OctGorzupia 15:23No data—
Wed 14 OctGorzupia 15:23No data—
Tue 13 OctGorzupia 15:230 min—
Mon 12 OctGorzupia 15:230 min—
Sun 11 OctGorzupia 15:51No data—
Sat 10 OctGorzupia 15:51No data—
Fri 9 OctGorzupia 15:51No data—
Thu 8 OctGorzupia 15:52+1 min+1 min
Wed 7 OctGorzupia 15:510 min—