REG 60605 Nysa → Brzeg
Alerts for train 60605
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line REG.
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 23 Nov 2026, 00:00 (GMT+1).
An alert on this phone or computer when the 60605 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Sunday 22 November −5 min
Next service: Saturday 17:48 from Nysa · Sat 28 Nov
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:48 | on 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:52 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Brzeg 18:48 | −5 min | — |
| Sat 21 Nov | Brzeg 18:53 | 0 min | — |
| Sun 15 Nov | Brzeg 18:49 | −3 min | — |
| Sat 14 Nov | Brzeg 18:53 | 0 min | — |
| Wed 11 Nov | Brzeg 18:53 | 0 min | — |
| Sun 8 Nov | Brzeg 18:53 | 0 min | — |
| Sat 7 Nov | Brzeg 18:53 | 0 min | — |
| Sun 1 Nov | Brzeg 18:59 | +7 min | +10 min |
| Sat 31 Oct | Brzeg 18:54 | 0 min | — |
| Sun 25 Oct | Brzeg 18:53 | No data | — |
| Sat 24 Oct | Brzeg 18:48 | No data | — |
| Sun 18 Oct | Brzeg 18:46 | −2 min | — |
| Sat 17 Oct | Brzeg 18:48 | 0 min | — |
| Sun 11 Oct | Brzeg 18:49 | +1 min | +1 min |
| Sat 10 Oct | Brzeg 18:50 | +1 min | +1 min |
| Sun 4 Oct | Brzeg 18:48 | −1 min | — |
| Sat 3 Oct | Brzeg 18:47 | +3 min | +3 min |
| Sun 27 Sept | Brzeg 18:47 | −1 min | — |
| Sat 26 Sept | Brzeg 18:46 | No data | — |
| Sun 20 Sept | Brzeg 18:46 | No data | — |
| Sat 19 Sept | Brzeg 18:47 | No data | — |
| Sun 13 Sept | Brzeg 18:46 | +1 min | +1 min |
| Sat 12 Sept | Brzeg 18:46 | +1 min | +1 min |
| Sun 6 Sept | Brzeg 18:46 | +1 min | +1 min |
| Sat 5 Sept | Brzeg 18:47 | No data | — |
| Sun 30 Aug | Brzeg 18:46 | No data | — |