REG 64336 Opole Główne – Gliwice

View line REG

Opole Główne 16:26 → Gliwice 17:37 Mon, Tue, Wed, Thu, Fri 1 h 11 min · 15 stops PolRegio

It has not run yet today

Last recorded run: Tuesday 10 November +9 min

Next service: today 16:26 from Opole Główne · Thu 12 Nov

Next departure 16:26 today · Opole Główne
On-time · 30 days
53%
8/15 runs under 3 min
RT coverage: 15 full · 0 partial · 5 no data
On-time · 90 days
56%
23/41 runs under 3 min
RT coverage: 41 full · 0 partial · 11 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
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

  • Fri 30 Oct Max en route +13 min · last fix heading to Gliwice +13 min
  • Tue 10 Nov Max en route +9 min · last fix heading to Gliwice +9 min
  • Mon 9 Nov Max en route +9 min · last fix heading to Gliwice +9 min
  • Tue 13 Oct Max en route +7 min · last fix heading to Gliwice +7 min
  • Mon 12 Oct Max en route +7 min · last fix heading to Gliwice +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 56% · 23
  • 3–10 min 41% · 17
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 43% M n=7
  • 33% T n=9
  • 75% W n=8
  • 78% T n=9
  • 50% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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
16:26on time +3 min
16:30≈ +1 min ≈ +3 min
16:39≈ +1 min ≈ +3 min
16:43≈ +1 min ≈ +3 min
16:49 / 16:50≈ +2 min ≈ +4 min
16:55 / 16:56≈ +2 min ≈ +4 min
17:02≈ +2 min ≈ +4 min
17:05 / 17:06≈ +2 min ≈ +4 min
17:08 / 17:09≈ +2 min ≈ +4 min
17:12 / 17:13≈ +2 min ≈ +5 min
17:17 / 17:18≈ +2 min ≈ +5 min
17:22≈ +2 min ≈ +6 min
17:25 / 17:26≈ +2 min ≈ +6 min
17:29≈ +2 min ≈ +6 min
17:37+2 min +7 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 NovGliwice 17:47+9 min+9 min
Mon 9 NovGliwice 17:47+9 min+9 min
Fri 6 NovGliwice 17:390 min—
Thu 5 NovGliwice 17:380 min—
Wed 4 NovGliwice 17:380 min—
Tue 3 NovGliwice 17:38−1 min—
Mon 2 NovGliwice 17:380 min—
Fri 30 OctGliwice 17:51+13 min+13 min
Thu 29 OctGliwice 17:41+3 min+3 min
Wed 28 OctGliwice 17:380 min—
Tue 27 OctGliwice 17:41+3 min+3 min
Mon 26 OctGliwice 17:44+5 min+5 min
Fri 23 OctGliwice 17:40No data—
Thu 22 OctGliwice 17:40No data—
Wed 21 OctGliwice 17:39No data—
Tue 20 OctGliwice 17:39No data—
Mon 19 OctGliwice 17:39No data—
Fri 16 OctGliwice 17:42+5 min+5 min
Thu 15 OctGliwice 17:390 min—
Wed 14 OctGliwice 17:390 min—
Tue 13 OctGliwice 17:46+7 min+7 min
Mon 12 OctGliwice 17:46+7 min+7 min
Fri 9 OctGliwice 17:390 min—
Thu 8 OctGliwice 17:400 min—
Wed 7 OctGliwice 17:390 min—
Tue 6 OctGliwice 17:390 min—
Mon 5 OctGliwice 17:40+1 min+1 min
Fri 2 OctGliwice 17:37No data—
Thu 1 OctGliwice 17:37+2 min+2 min
Wed 30 SeptGliwice 17:38+4 min+4 min