REG 60614 Brzeg – Nysa

View line REG

Brzeg 15:18 → Nysa 16:22 Sat, Sun 1 h 04 min · 11 stops PKP

It does not run today

Last recorded run: Sunday 4 October 0 min

Next service: tomorrow 15:18 from Brzeg · Sat 10 Oct

Next departure 15:18 tomorrow · 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/11 runs with data)
RT coverage: 2 full · 0 partial · 9 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

Worst days

  • Sun 27 Sept Max en route +3 min · last fix heading to Nysa +3 min

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 50% · 1
  • 3–10 min 50% · 1
  • 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
  • 50% S n=2

Stops and timetable

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

StopSched.
15:18
15:26 / 15:27
15:31 / 15:32
15:36
15:43 / 15:44
15:50
15:56 / 15:57
16:00
16:06 / 16:07
16:11 / 16:12
16:22

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 4 OctNysa 16:230 min—
Sat 3 OctNysa 16:22No data—
Sun 27 SeptNysa 16:22+3 min+3 min
Sat 26 SeptNysa 16:21No data—
Sun 20 SeptNysa 16:21No data—
Sat 19 SeptNysa 16:22No data—
Sun 13 SeptNysa 16:21No data—
Sat 12 SeptNysa 16:21No data—
Sun 6 SeptNysa 16:21No data—
Sat 5 SeptNysa 16:21No data—
Sun 30 AugNysa 16:21No data—