KW 70209 Jarocin – Gniezno

View line KW

Jarocin 21:03 → Gniezno 22:06 Mon, Tue, Thu, Fri 1 h 03 min · 14 stops Koleje Wielkopolskie

Running now · updated 22:08

Between Gębarzewo and Gniezno +5 min

Estimated arrival at Gniezno 22:11 22:06 · 61 km/h

  1. Jarocin21:03
  2. Żerków21:12
  3. Miłosław21:23
  4. Obłaczkowo21:34
  5. Marzenin21:48
  6. Gębarzewo21:59
  7. Gniezno22:06

Today it is running worse than usual: typical arrival delay is +2 min; 53% of the last 17 runs arrived on time.

On-time · 30 days
53%
9/17 runs under 3 min
RT coverage: 17 full · 0 partial · 5 no data
On-time · 90 days
50%
14/28 runs under 3 min
RT coverage: 28 full · 0 partial · 9 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

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

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

Worst days

  • Mon 12 Oct Max en route +10 min · last fix heading to Gniezno +10 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Gniezno +5 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Gniezno +5 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Gniezno +5 min
  • Tue 13 Oct Max en route +5 min · last fix heading to Gniezno +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 50% · 14
  • 3–10 min 46% · 13
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=6
  • 50% T n=6
  • 60% W n=5
  • 40% T n=5
  • 50% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 28 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
21:03on time +4 minPassed
21:08 / 21:09≈ on time ≈ +3 minPassed
21:12≈ on time ≈ +3 minPassed
21:17 / 21:18≈ +1 min ≈ +3 minPassed
21:23 / 21:24≈ +1 min ≈ +4 minPassed
21:27≈ +1 min ≈ +4 minPassed
21:31 / 21:32≈ +1 min ≈ +4 minPassed
21:34≈ +1 min ≈ +4 minPassed
21:39 / 21:43≈ +2 min ≈ +4 minPassed
21:48≈ +2 min ≈ +4 minPassed
21:52≈ +2 min ≈ +4 minPassed
21:55 / 21:56≈ +2 min ≈ +4 minPassed
21:59≈ +2 min ≈ +4 minPassed
22:06+2 min +5 minNext

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 NovGniezno 22:04+5 min+5 min
Mon 9 NovGniezno 22:12+5 min+5 min
Fri 6 NovGniezno 22:09+3 min+3 min
Thu 5 NovGniezno 22:09+3 min+3 min
Wed 4 NovGniezno 22:070 min—
Tue 3 NovGniezno 22:09+2 min+2 min
Mon 2 NovGniezno 22:080 min—
Fri 30 OctGniezno 22:070 min—
Thu 29 OctGniezno 22:070 min—
Wed 28 OctGniezno 22:070 min+1 min
Tue 27 OctGniezno 22:070 min—
Mon 26 OctGniezno 22:080 min+2 min
Fri 23 OctGniezno 21:52No data—
Thu 22 OctGniezno 21:51No data—
Wed 21 OctGniezno 21:51No data—
Tue 20 OctGniezno 21:51No data—
Mon 19 OctGniezno 21:51No data—
Fri 16 OctGniezno 21:510 min—
Thu 15 OctGniezno 21:57+5 min+5 min
Wed 14 OctGniezno 21:55+4 min+4 min
Tue 13 OctGniezno 21:56+5 min+5 min
Mon 12 OctGniezno 22:04+10 min+10 min
Fri 9 OctGniezno 21:57+3 min+3 min
Thu 8 OctGniezno 21:540 min—
Wed 7 OctGniezno 21:540 min—
Tue 6 OctGniezno 21:540 min—
Mon 5 OctGniezno 21:540 min—
Fri 2 OctGniezno 21:52+4 min+4 min
Thu 1 OctGniezno 21:52No data—
Wed 30 SeptGniezno 21:52No data—