REG 60605 Nysa → Brzeg

View line REG

Nysa 17:48 → Brzeg 18:52 Sat, Sun 1 h 04 min · 11 stops PolRegio

REG 60605 Nysa–Brzeg: final delay under 3 min on 8 of its 9 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 23:53 (GMT+1).

✓ Today’s run finished

Today it reached Brzeg at 18:52 −5 min

  1. Nysa17:48
  2. Pakosławice18:01
  3. Skoroszyce18:08
  4. Stary Grodków18:18
  5. Lipowa Śląska18:32
  6. Czeska Wieś18:37
  7. Brzeg18:52

Next service: Saturday 17:48 from Nysa · Sat 28 Nov

Next departure 17:48 Saturday · Nysa
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 2 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Brzeg, 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 1 Nov Max en route +10 min · last fix heading to Brzeg +7 min
  • Sat 3 Oct Max en route +3 min · last fix heading to Brzeg +3 min

Distribution · 90 days

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

  • Early 16% · 3
  • On time 74% · 14
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 88% S n=8
  • 90% S n=10

Stops and timetable

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

Last 90 days, 19 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
17:48on time +1 min
17:57≈ on time ≈ +1 min
18:01 / 18:02≈ on time ≈ +1 min
18:08≈ on time ≈ +1 min
18:11 / 18:12≈ on time ≈ +1 min
18:18≈ on time ≈ +1 min
18:24 / 18:25≈ on time ≈ +1 min
18:32 / 18:33≈ on time ≈ +1 min
18:37≈ on time ≈ +1 min
18:42≈ on time ≈ +1 min
18:52on time +1 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
Sun 22 NovBrzeg 18:48−5 min—
Sat 21 NovBrzeg 18:530 min—
Sun 15 NovBrzeg 18:49−3 min—
Sat 14 NovBrzeg 18:530 min—
Wed 11 NovBrzeg 18:530 min—
Sun 8 NovBrzeg 18:530 min—
Sat 7 NovBrzeg 18:530 min—
Sun 1 NovBrzeg 18:59+7 min+10 min
Sat 31 OctBrzeg 18:540 min—
Sun 25 OctBrzeg 18:53No data—
Sat 24 OctBrzeg 18:48No data—
Sun 18 OctBrzeg 18:46−2 min—
Sat 17 OctBrzeg 18:480 min—
Sun 11 OctBrzeg 18:49+1 min+1 min
Sat 10 OctBrzeg 18:50+1 min+1 min
Sun 4 OctBrzeg 18:48−1 min—
Sat 3 OctBrzeg 18:47+3 min+3 min
Sun 27 SeptBrzeg 18:47−1 min—
Sat 26 SeptBrzeg 18:46No data—
Sun 20 SeptBrzeg 18:46No data—
Sat 19 SeptBrzeg 18:47No data—
Sun 13 SeptBrzeg 18:46+1 min+1 min
Sat 12 SeptBrzeg 18:46+1 min+1 min
Sun 6 SeptBrzeg 18:46+1 min+1 min
Sat 5 SeptBrzeg 18:47No data—
Sun 30 AugBrzeg 18:46No data—