REG 60612 Brzeg – Nysa

View line REG

Brzeg 08:25 → Nysa 09:29 Sat, Sun 1 h 04 min · 11 stops PKP

It does not run today

Last recorded run: Sunday 11 October 0 min

Next service: Saturday 08:25 from Brzeg · Sat 17 Oct

Next departure 08:25 Saturday · Brzeg
On-time · 30 days
—
Too little data (2/8 runs with data)
RT coverage: 2 full · 0 partial · 6 no data
On-time · 90 days
—
Too little data (2/13 runs with data)
RT coverage: 2 full · 0 partial · 11 no data
Typical delay
—
Needs at least 5 runs with data (2 so far)
P90
—
Needs at least 5 runs with data (2 so far)

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 2
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
08:25
08:33 / 08:34
08:38 / 08:39
08:43
08:51
08:57 / 08:58
09:04
09:07 / 09:08
09:14
09:18 / 09:19
09:29

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.

Recent runs

DateLast stopFinalMax
Sun 11 OctNysa 09:300 min—
Sat 10 OctNysa 09:30No data—
Sun 4 OctNysa 09:300 min—
Sat 3 OctNysa 09:28No data—
Sun 27 SeptNysa 09:28No data—
Sat 26 SeptNysa 09:28No data—
Sun 20 SeptNysa 09:28No data—
Sat 19 SeptNysa 09:28No data—
Sun 13 SeptNysa 09:29No data—
Sat 12 SeptNysa 09:28No data—
Sun 6 SeptNysa 09:28No data—
Sat 5 SeptNysa 09:28No data—
Sun 30 AugNysa 09:28No data—