REG 60603 Nysa – Brzeg
Alerts for train 60603
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.
It does not run today
Last recorded run: Sunday 1 November +9 min
Next service: Saturday 10:45 from Nysa · Sat 7 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 +9 min
- Sun 4 Oct Max en route +9 min · last fix heading to Brzeg +9 min
- Sat 3 Oct Max en route +8 min · last fix heading to Brzeg +8 min
- Sun 18 Oct Max en route +3 min · last fix heading to Brzeg +3 min
- Sat 17 Oct Max en route +3 min · last fix heading to Brzeg +3 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 30% · 3
- On time 20% · 2
- 3–10 min 50% · 5
- 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
- 50% S n=4
- 50% S n=6
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 10 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 |
|---|---|---|---|
| 10:45 | on time | +9 min | |
| 10:55 | ≈ on time | ≈ +9 min | |
| 10:59 / 11:00 | ≈ on time | ≈ +9 min | |
| 11:06 | ≈ on time | ≈ +9 min | |
| 11:09 / 11:10 | ≈ +1 min | ≈ +9 min | |
| 11:16 | ≈ +1 min | ≈ +9 min | |
| 11:22 / 11:23 | ≈ +1 min | ≈ +9 min | |
| 11:30 | ≈ +1 min | ≈ +9 min | |
| 11:34 / 11:35 | ≈ +1 min | ≈ +9 min | |
| 11:40 | ≈ +1 min | ≈ +9 min | |
| 11:50 | +2 min | +9 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 1 Nov | Brzeg 12:00 | +9 min | +10 min |
| Sat 31 Oct | Brzeg 11:51 | 0 min | — |
| Sun 25 Oct | Brzeg 11:51 | No data | — |
| Sat 24 Oct | Brzeg 12:09 | No data | — |
| Sun 18 Oct | Brzeg 12:12 | +3 min | +3 min |
| Sat 17 Oct | Brzeg 12:12 | +3 min | +3 min |
| Sun 11 Oct | Brzeg 12:06 | −3 min | — |
| Sat 10 Oct | Brzeg 12:09 | 0 min | — |
| Sun 4 Oct | Brzeg 12:18 | +9 min | +9 min |
| Sat 3 Oct | Brzeg 12:08 | +8 min | +8 min |
| Sun 27 Sept | Brzeg 12:07 | −3 min | — |
| Sat 26 Sept | Brzeg 12:07 | No data | — |
| Sun 20 Sept | Brzeg 12:07 | No data | — |
| Sat 19 Sept | Brzeg 12:07 | No data | — |
| Sun 13 Sept | Brzeg 12:07 | No data | — |
| Sat 12 Sept | Brzeg 12:07 | No data | — |
| Sun 6 Sept | Brzeg 12:07 | −2 min | — |
| Sat 5 Sept | Brzeg 12:07 | No data | — |
| Sun 30 Aug | Brzeg 12:07 | No data | — |