REG 60907 Opole Główne – Kluczbork
Alerts for train 60907
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line REG.
It has not run yet today
Last recorded run: Thursday 12 November 0 min
Next service: today 15:37 from Opole Główne · Fri 13 Nov
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
- Fri 9 Oct Max en route +9 min · last fix heading to Kluczbork +9 min
- Fri 6 Nov Max en route +3 min · last fix heading to Kluczbork +3 min
Distribution · 90 days
23 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 91% · 21
- 3–10 min 9% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=4
- 100% T n=5
- 50% F n=4
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 23 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 15:37 | on time | on time | |
| 15:42 | ≈ on time | ≈ on time | |
| 15:48 | ≈ on time | ≈ on time | |
| 15:51 | ≈ on time | ≈ on time | |
| 15:55 / 15:56 | ≈ on time | ≈ on time | |
| 16:00 | ≈ on time | ≈ on time | |
| 16:03 / 16:04 | ≈ on time | ≈ on time | |
| 16:06 | ≈ on time | ≈ on time | |
| 16:09 | ≈ on time | ≈ on time | |
| 16:14 | ≈ on time | ≈ on time | |
| 16:21 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 12 Nov | Kluczbork 16:22 | 0 min | — |
| Tue 10 Nov | Kluczbork 16:23 | 0 min | — |
| Mon 9 Nov | Kluczbork 16:22 | 0 min | — |
| Fri 6 Nov | Kluczbork 16:24 | +3 min | +3 min |
| Thu 5 Nov | Kluczbork 16:22 | 0 min | — |
| Wed 4 Nov | Kluczbork 16:22 | 0 min | — |
| Tue 3 Nov | Kluczbork 16:23 | 0 min | — |
| Mon 2 Nov | Kluczbork 16:22 | 0 min | — |
| Fri 30 Oct | Kluczbork 16:22 | 0 min | — |
| Thu 29 Oct | Kluczbork 16:22 | 0 min | — |
| Wed 28 Oct | Kluczbork 16:22 | 0 min | — |
| Tue 27 Oct | Kluczbork 16:22 | 0 min | — |
| Mon 26 Oct | Kluczbork 16:23 | 0 min | — |
| Fri 23 Oct | Kluczbork 16:22 | No data | — |
| Thu 22 Oct | Kluczbork 16:23 | No data | — |
| Wed 21 Oct | Kluczbork 16:23 | No data | — |
| Tue 20 Oct | Kluczbork 16:22 | No data | — |
| Mon 19 Oct | Kluczbork 16:22 | No data | — |
| Fri 16 Oct | Kluczbork 16:22 | 0 min | — |
| Thu 15 Oct | Kluczbork 16:22 | 0 min | — |
| Wed 14 Oct | Kluczbork 16:22 | 0 min | — |
| Tue 13 Oct | Kluczbork 16:23 | 0 min | — |
| Mon 12 Oct | Kluczbork 16:22 | 0 min | — |
| Fri 9 Oct | Kluczbork 16:31 | +9 min | +9 min |
| Thu 8 Oct | Kluczbork 16:22 | 0 min | — |
| Wed 7 Oct | Kluczbork 16:22 | 0 min | — |
| Tue 6 Oct | Kluczbork 16:22 | 0 min | — |
| Mon 5 Oct | Kluczbork 16:23 | 0 min | — |
| Fri 2 Oct | Kluczbork 16:20 | No data | — |
| Thu 1 Oct | Kluczbork 16:21 | No data | — |