REG 60616 Brzeg – Nysa

View line REG

Brzeg 16:19 → Nysa 17:23 Mon, Tue, Wed, Thu, Fri 1 h 04 min · 11 stops PolRegio

It has not run yet today

Last recorded run: Tuesday 17 November +8 min

Next service: today 16:19 from Brzeg · Wed 18 Nov

Next departure 16:19 today · Brzeg
On-time · 30 days
69%
11/16 runs under 3 min
RT coverage: 16 full · 0 partial · 4 no data
On-time · 90 days
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 16 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
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 2 Oct Max en route +17 min · last fix heading to Pakosławice +17 min
  • Tue 10 Nov Max en route +18 min · last fix heading to Nysa +14 min
  • Tue 17 Nov Max en route +8 min · last fix heading to Nysa +8 min
  • Mon 16 Nov Max en route +17 min · last fix heading to Nysa +7 min
  • Thu 29 Oct Max en route +13 min · last fix heading to Nysa +6 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 78% · 31
  • 3–10 min 13% · 5
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 78% T n=9
  • 100% W n=6
  • 89% T n=9
  • 70% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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:19on time +3 min
16:27 / 16:28≈ on time ≈ +3 min
16:32 / 16:33≈ on time ≈ +3 min
16:37≈ on time ≈ +3 min
16:44 / 16:45≈ on time ≈ +3 min
16:51≈ on time ≈ +4 min
16:57 / 16:58≈ on time ≈ +4 min
17:01≈ on time ≈ +5 min
17:07 / 17:08≈ on time ≈ +5 min
17:12≈ on time ≈ +5 min
17:23on time +5 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 17 NovNysa 17:32+8 min+8 min
Mon 16 NovNysa 17:32+7 min+17 min
Fri 13 NovNysa 17:240 min—
Thu 12 NovNysa 17:240 min—
Tue 10 NovNysa 17:24+14 min+18 min
Mon 9 NovNysa 17:240 min—
Fri 6 NovNysa 17:27+3 min+3 min
Thu 5 NovNysa 17:240 min—
Wed 4 NovNysa 17:240 min—
Tue 3 NovNysa 17:24+2 min+2 min
Mon 2 NovNysa 17:240 min—
Fri 30 OctNysa 17:26+2 min+2 min
Thu 29 OctNysa 17:30+6 min+13 min
Wed 28 OctNysa 17:240 min—
Tue 27 OctNysa 17:240 min—
Mon 26 OctNysa 17:250 min—
Fri 23 OctNysa 17:25No data—
Thu 22 OctNysa 17:25No data—
Wed 21 OctNysa 17:25No data—
Tue 20 OctNysa 17:24No data—
Mon 19 OctNysa 17:24No data—
Fri 16 OctNysa 17:240 min—
Thu 15 OctNysa 17:22−2 min—
Wed 14 OctNysa 17:23−1 min—
Tue 13 OctNysa 17:240 min—
Mon 12 OctNysa 17:240 min—
Fri 9 OctNysa 17:240 min—
Thu 8 OctNysa 17:250 min—
Wed 7 OctNysa 17:240 min—
Tue 6 OctNysa 17:240 min—