REG 66623 Opole Główne – Nysa

View line REG

Opole Główne 15:42 → Nysa 16:40 Mon, Tue, Wed, Thu, Fri 0 h 58 min · 17 stops PolRegio

✓ Today’s run finished

Today it reached Nysa at 16:40 0 min

  1. Opole Główne15:42
  2. Komprachcice15:52
  3. Szydłów16:00
  4. Sowin16:12
  5. Jasienica Dolna16:23
  6. Kubice16:29
  7. Nysa16:40

Next service: tomorrow 15:42 from Opole Główne · Fri 13 Nov

Next departure 15:42 tomorrow · Opole Główne
On-time · 30 days
22%
2/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
22%
2/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
Typical delay
+5min
Median at arrival, 90 days
30 days: +5 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Nysa, 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 6 Nov Max en route +10 min · last fix heading to Nysa +10 min
  • Tue 10 Nov Max en route +8 min · last fix heading to Nysa +8 min
  • Thu 5 Nov Max en route +8 min · last fix heading to Nysa +8 min
  • Wed 4 Nov Max en route +8 min · last fix heading to Nysa +8 min
  • Tue 3 Nov Max en route +5 min · last fix heading to Nysa +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 22% · 2
  • 3–10 min 67% · 6
  • 10–30 min 11% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 0% T n=2
  • 0% W n=1
  • 50% T n=2
  • 0% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 9 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
15:42on time +8 min
15:45≈ on time ≈ +8 min
15:49≈ +1 min ≈ +8 min
15:52 / 15:53≈ +1 min ≈ +8 min
15:59≈ +2 min ≈ +8 min
16:00 / 16:01≈ +2 min ≈ +8 min
16:06≈ +3 min ≈ +8 min
16:09 / 16:10≈ +4 min ≈ +8 min
16:12 / 16:13≈ +4 min ≈ +8 min
16:17≈ +5 min ≈ +8 min
16:20≈ +5 min ≈ +8 min
16:23≈ +5 min ≈ +8 min
16:26 / 16:27≈ +5 min ≈ +8 min
16:29 / 16:30≈ +5 min ≈ +8 min
16:33≈ +5 min ≈ +8 min
16:36≈ +5 min ≈ +8 min
16:40+5 min +8 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 NovNysa 16:390 min—
Tue 10 NovNysa 16:49+8 min+8 min
Mon 9 NovNysa 16:43+2 min+2 min
Fri 6 NovNysa 16:49+10 min+10 min
Thu 5 NovNysa 16:49+8 min+8 min
Wed 4 NovNysa 16:49+8 min+8 min
Tue 3 NovNysa 16:45+5 min+5 min
Mon 2 NovNysa 16:44+5 min+5 min
Fri 30 OctNysa 16:45+4 min+4 min