REG 76510 Kępno – Kluczbork

View line REG

Kępno 04:45 → Kluczbork 05:20 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 8 stops PolRegio

It does not run today

Last recorded run: Tuesday 10 November 0 min

Next service: tomorrow 04:45 from Kępno · Thu 12 Nov

Next departure 04:45 tomorrow · Kępno
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 17 full · 0 partial · 4 no data
On-time · 90 days
74%
20/27 runs under 3 min
RT coverage: 27 full · 0 partial · 6 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +11 min

Last 30 days

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

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

Worst days

  • Thu 5 Nov Max en route +12 min · last fix heading to Kluczbork +12 min
  • Fri 6 Nov Max en route +11 min · last fix heading to Kluczbork +11 min
  • Tue 13 Oct Max en route +11 min · last fix heading to Kluczbork +11 min
  • Mon 12 Oct Max en route +11 min · last fix heading to Kluczbork +11 min
  • Fri 2 Oct Max en route +3 min · last fix heading to Kluczbork +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 74% · 20
  • 3–10 min 11% · 3
  • 10–30 min 15% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 67% T n=6
  • 100% W n=4
  • 60% T n=5
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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
04:45on time +6 min
04:49 / 04:50≈ on time ≈ +6 min
04:54≈ on time ≈ +6 min
04:59 / 05:00≈ on time ≈ +7 min
05:05≈ +1 min ≈ +8 min
05:09≈ +1 min ≈ +9 min
05:13 / 05:14≈ +1 min ≈ +10 min
05:20+1 min +11 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 NovKluczbork 05:220 min—
Mon 9 NovKluczbork 05:22+1 min+1 min
Fri 6 NovKluczbork 05:32+11 min+11 min
Thu 5 NovKluczbork 05:33+12 min+12 min
Wed 4 NovKluczbork 05:190 min—
Tue 3 NovKluczbork 05:190 min—
Mon 2 NovKluczbork 05:190 min—
Fri 30 OctKluczbork 05:210 min—
Thu 29 OctKluczbork 05:22+1 min+1 min
Wed 28 OctKluczbork 05:23+2 min+2 min
Tue 27 OctKluczbork 05:24+2 min+2 min
Mon 26 OctKluczbork 05:22+1 min+1 min
Fri 23 OctKluczbork 05:22No data—
Thu 22 OctKluczbork 05:22No data—
Wed 21 OctKluczbork 05:22No data—
Tue 20 OctKluczbork 05:22No data—
Mon 19 OctKluczbork 05:220 min—
Fri 16 OctKluczbork 05:230 min—
Thu 15 OctKluczbork 05:220 min—
Wed 14 OctKluczbork 05:23+1 min+1 min
Tue 13 OctKluczbork 05:33+11 min+11 min
Mon 12 OctKluczbork 05:33+11 min+11 min
Fri 9 OctKluczbork 05:220 min—
Thu 8 OctKluczbork 05:230 min—
Wed 7 OctKluczbork 05:220 min—
Tue 6 OctKluczbork 05:220 min—
Mon 5 OctKluczbork 05:24+1 min+1 min
Fri 2 OctKluczbork 05:20+3 min+3 min
Thu 1 OctKluczbork 05:20+3 min+3 min
Wed 30 SeptKluczbork 05:20No data—