REG 60601 Nysa → Brzeg

View line REG

Nysa 04:54 → Brzeg 05:58 Daily 1 h 04 min · 11 stops PolRegio

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

✓ Today’s run finished

Today it reached Brzeg at 05:58 −2 min

  1. Nysa04:54
  2. Pakosławice05:08
  3. Skoroszyce05:14
  4. Stary Grodków05:24
  5. Lipowa Śląska05:38
  6. Czeska Wieś05:43
  7. Brzeg05:58

Next service: tomorrow 04:54 from Nysa · Mon 23 Nov

Next departure 04:54 tomorrow · Nysa
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 52 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 +34 min · last fix heading to Brzeg +34 min
  • Fri 9 Oct Max en route +16 min · last fix heading to Brzeg +16 min

Distribution · 90 days

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

  • Early 31% · 16
  • On time 65% · 34
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% T n=11
  • 83% F n=6
  • 100% S n=4
  • 86% S n=7

Stops and timetable

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

Last 90 days, 52 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
04:54on time on time
05:04≈ on time ≈ on time
05:08 / 05:09≈ on time ≈ on time
05:14 / 05:15≈ on time ≈ on time
05:18≈ on time ≈ on time
05:24 / 05:25≈ on time ≈ on time
05:31≈ on time ≈ on time
05:38 / 05:39≈ on time ≈ on time
05:43≈ on time ≈ on time
05:48 / 05:49≈ on time ≈ on time
05:58on time on time

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 05:57−2 min—
Sat 21 NovBrzeg 05:590 min—
Fri 20 NovBrzeg 05:53−2 min—
Thu 19 NovBrzeg 05:540 min—
Wed 18 NovBrzeg 05:54No data—
Tue 17 NovBrzeg 05:540 min—
Mon 16 NovBrzeg 05:540 min—
Sun 15 NovBrzeg 05:590 min—
Sat 14 NovBrzeg 05:590 min—
Fri 13 NovBrzeg 05:57+2 min+2 min
Thu 12 NovBrzeg 05:540 min—
Wed 11 NovBrzeg 05:59No data—
Tue 10 NovBrzeg 05:54No data—
Mon 9 NovBrzeg 05:540 min—
Sun 8 NovBrzeg 05:590 min—
Sat 7 NovBrzeg 05:59No data—
Fri 6 NovBrzeg 05:54No data—
Thu 5 NovBrzeg 05:540 min—
Wed 4 NovBrzeg 05:540 min—
Tue 3 NovBrzeg 05:540 min—
Mon 2 NovBrzeg 05:540 min—
Sun 1 NovBrzeg 06:33+34 min+34 min
Sat 31 OctBrzeg 05:590 min—
Fri 30 OctBrzeg 05:550 min—
Thu 29 OctBrzeg 05:52−3 min—
Wed 28 OctBrzeg 05:550 min—
Tue 27 OctBrzeg 05:550 min—
Mon 26 OctBrzeg 05:550 min—
Sun 25 OctBrzeg 05:59No data—
Sat 24 OctBrzeg 06:00No data—