REG 60903 Opole Główne – Kluczbork

View line REG

Opole Główne 10:13 → Kluczbork 10:57 Mon, Tue, Wed, Thu, Fri 0 h 44 min · 11 stops PolRegio

✓ Today’s run finished

Today it reached Kluczbork at 10:57 0 min

  1. Opole Główne10:13
  2. Kotórz Mały10:24
  3. Osowiec Przystanek10:27
  4. Kały10:36
  5. Tuły10:42
  6. Bukowo10:45
  7. Kluczbork10:57

Next service: tomorrow 10:13 from Opole Główne · Fri 20 Nov

Next departure 10:13 tomorrow · Opole Główne
On-time · 30 days
59%
10/17 runs under 3 min
RT coverage: 17 full · 0 partial · 4 no data
On-time · 90 days
69%
25/36 runs under 3 min
RT coverage: 36 full · 0 partial · 12 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+12min
9 in 10 runs arrive with less than this
30 days: +15 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

  • Tue 3 Nov Max en route +19 min · last fix heading to Kluczbork +19 min
  • Mon 2 Nov Max en route +17 min · last fix heading to Kluczbork +17 min
  • Tue 29 Sept Max en route +15 min · last fix heading to Tuły +15 min
  • Mon 9 Nov Max en route +18 min · last fix heading to Kluczbork +14 min
  • Mon 28 Sept Max en route +11 min · last fix heading to Borkowice +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 69% · 25
  • 3–10 min 17% · 6
  • 10–30 min 14% · 5
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 71% T n=7
  • 71% W n=7
  • 86% T n=7
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
10:13on time +8 min
10:18≈ on time ≈ +8 min
10:24≈ on time ≈ +8 min
10:27≈ on time ≈ +8 min
10:31 / 10:32≈ on time ≈ +8 min
10:36≈ on time ≈ +9 min
10:39 / 10:40≈ on time ≈ +10 min
10:42≈ on time ≈ +10 min
10:45≈ on time ≈ +11 min
10:50≈ on time ≈ +11 min
10:57on time +12 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 19 NovKluczbork 10:580 min—
Wed 18 NovKluczbork 10:580 min—
Tue 17 NovKluczbork 10:580 min—
Mon 16 NovKluczbork 10:590 min—
Fri 13 NovKluczbork 11:03+5 min+5 min
Thu 12 NovKluczbork 11:03+5 min+13 min
Tue 10 NovKluczbork 10:58No data—
Mon 9 NovKluczbork 11:12+14 min+18 min
Fri 6 NovKluczbork 11:03+5 min+5 min
Thu 5 NovKluczbork 10:580 min—
Wed 4 NovKluczbork 10:59+3 min+3 min
Tue 3 NovKluczbork 11:17+19 min+19 min
Mon 2 NovKluczbork 11:14+17 min+17 min
Fri 30 OctKluczbork 10:580 min—
Thu 29 OctKluczbork 10:580 min—
Wed 28 OctKluczbork 10:580 min—
Tue 27 OctKluczbork 10:580 min—
Mon 26 OctKluczbork 10:580 min—
Fri 23 OctKluczbork 11:00No data—
Thu 22 OctKluczbork 11:00No data—
Wed 21 OctKluczbork 11:00No data—
Tue 20 OctKluczbork 11:01No data—
Mon 19 OctKluczbork 11:010 min—
Fri 16 OctKluczbork 11:000 min—
Thu 15 OctKluczbork 11:000 min—
Wed 14 OctKluczbork 11:010 min—
Tue 13 OctKluczbork 11:000 min—
Mon 12 OctKluczbork 11:01+1 min+1 min
Fri 9 OctKluczbork 11:010 min—
Thu 8 OctKluczbork 11:000 min—