REG 64342 Opole Główne – Gliwice

View line REG

Opole Główne 21:22 → Gliwice 22:38 Daily 1 h 16 min · 15 stops PolRegio

✓ Today’s run finished

Today it reached Gliwice at 22:38 0 min

  1. Opole Główne21:22
  2. Tarnów Opolski21:35
  3. Strzelce Opolskie21:51
  4. Kotulin22:03
  5. Toszek22:10
  6. Gliwice Kuźnica22:27
  7. Gliwice22:38

Next service: tomorrow 21:22 from Opole Główne · Fri 13 Nov

Next departure 21:22 tomorrow · Opole Główne
On-time · 30 days
74%
17/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
65%
36/55 runs under 3 min
RT coverage: 55 full · 0 partial · 20 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +9 min

Last 30 days

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

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

Worst days

  • Wed 4 Nov Max en route +21 min · last fix heading to Gliwice +18 min
  • Mon 21 Sept Max en route +14 min · last fix heading to Gliwice Kuźnica +14 min
  • Mon 31 Aug Max en route +13 min · last fix heading to Gliwice Kuźnica +13 min
  • Fri 9 Oct Max en route +14 min · last fix heading to Gliwice +12 min
  • Sun 20 Sept Max en route +12 min · last fix heading to Gliwice Łabędy +12 min

Distribution · 90 days

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

  • Early 5% · 3
  • On time 60% · 33
  • 3–10 min 22% · 12
  • 10–30 min 13% · 7
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 78% T n=9
  • 75% W n=8
  • 88% T n=8
  • 57% F n=7
  • 43% S n=7
  • 38% S n=8

Stops and timetable

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

Last 90 days, 55 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
21:22on time +9 min
21:26≈ on time ≈ +9 min
21:35≈ on time ≈ +9 min
21:39≈ on time ≈ +9 min
21:45≈ on time ≈ +8 min
21:51 / 21:54≈ on time ≈ +9 min
22:00≈ +1 min ≈ +9 min
22:03 / 22:04≈ +1 min ≈ +9 min
22:06 / 22:07≈ +1 min ≈ +9 min
22:10 / 22:12≈ +1 min ≈ +9 min
22:16 / 22:17≈ +1 min ≈ +9 min
22:21 / 22:23≈ +1 min ≈ +10 min
22:27≈ +1 min ≈ +10 min
22:30≈ +1 min ≈ +10 min
22:38+1 min +10 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 12 NovGliwice 22:390 min—
Wed 11 NovGliwice 22:390 min—
Tue 10 NovGliwice 22:39+1 min+1 min
Mon 9 NovGliwice 22:390 min—
Sun 8 NovGliwice 22:39+1 min+1 min
Sat 7 NovGliwice 22:39+2 min+2 min
Fri 6 NovGliwice 22:390 min—
Thu 5 NovGliwice 22:390 min—
Wed 4 NovGliwice 22:57+18 min+21 min
Tue 3 NovGliwice 22:39+1 min+1 min
Mon 2 NovGliwice 22:38−1 min—
Sun 1 NovGliwice 22:44+7 min+12 min
Sat 31 OctGliwice 22:50+10 min+10 min
Fri 30 OctGliwice 22:48+9 min+11 min
Thu 29 OctGliwice 22:40+1 min+1 min
Wed 28 OctGliwice 22:390 min—
Tue 27 OctGliwice 22:390 min—
Mon 26 OctGliwice 22:400 min—
Sun 25 OctGliwice 22:39No data—
Sat 24 OctGliwice 22:37No data—
Fri 23 OctGliwice 22:37No data—
Thu 22 OctGliwice 22:36No data—
Wed 21 OctGliwice 22:36No data—
Tue 20 OctGliwice 22:36No data—
Mon 19 OctGliwice 22:36No data—
Sun 18 OctGliwice 22:41+5 min+5 min
Sat 17 OctGliwice 22:40+4 min+4 min
Fri 16 OctGliwice 22:360 min—
Thu 15 OctGliwice 22:38+1 min+1 min
Wed 14 OctGliwice 22:360 min—