KW 70216 Ostrów Wielkopolski – Kalisz

View line KW

Ostrów Wielkopolski 13:21 → Kalisz 13:43 Daily 0 h 22 min · 6 stops Koleje Wielkopolskie

✓ Today’s run finished

Today it reached Kalisz at 13:43 0 min

  1. Ostrów Wielkopolski13:21
  2. Czekanów13:27
  3. Ociąż13:31
  4. Nowe Skalmierzyce13:35
  5. Kalisz Szczypiorno13:38
  6. Kalisz13:43

Next service: tomorrow 13:21 from Ostrów Wielkopolski · Thu 19 Nov

Next departure 13:21 tomorrow · Ostrów Wielkopolski
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
92%
35/38 runs under 3 min
RT coverage: 38 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Kalisz, 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 +5 min · last fix heading to Kalisz +5 min
  • Sat 26 Sept Max en route +3 min · last fix heading to Kalisz +3 min
  • Fri 25 Sept Max en route +3 min · last fix heading to Kalisz +3 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 89% · 34
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
13:21on time on time
13:27≈ on time ≈ on time
13:31≈ on time ≈ on time
13:35≈ on time ≈ on time
13:38 / 13:39≈ on time ≈ on time
13:43on time on time

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
Wed 18 NovKalisz 13:440 min—
Tue 17 NovKalisz 13:440 min—
Mon 16 NovKalisz 13:440 min—
Sun 15 NovKalisz 13:440 min—
Sat 14 NovKalisz 13:43−1 min—
Fri 13 NovKalisz 13:440 min—
Thu 12 NovKalisz 13:440 min—
Wed 11 NovKalisz 13:43−1 min—
Tue 10 NovKalisz 13:440 min—
Mon 9 NovKalisz 13:440 min—
Sun 8 NovKalisz 13:440 min—
Sat 7 NovKalisz 13:440 min—
Fri 6 NovKalisz 13:440 min—
Thu 5 NovKalisz 13:43−1 min—
Wed 4 NovKalisz 13:440 min—
Tue 3 NovKalisz 13:450 min—
Mon 2 NovKalisz 13:440 min—
Sun 1 NovKalisz 13:49+5 min+5 min
Sat 31 OctKalisz 13:440 min—
Fri 30 OctKalisz 13:440 min—
Thu 29 OctKalisz 13:440 min—
Wed 28 OctKalisz 13:440 min—
Tue 27 OctKalisz 13:440 min—
Mon 26 OctKalisz 13:440 min—
Sun 25 OctKalisz 13:44No data—
Sat 24 OctKalisz 13:33No data—
Fri 23 OctKalisz 13:33No data—
Thu 22 OctKalisz 13:33No data—
Wed 21 OctKalisz 13:33No data—
Tue 20 OctKalisz 13:33No data—