Os 2273 2273 Znojmo – Retz
Alerts for train 2273
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 2273.
It has not run yet today
Last recorded run: Thursday 5 November No data
Next service: today 20:57 from Znojmo · Fri 6 Nov
Last 30 days
Arrival delay at Retz, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 10 Sept Max en route +26 min · last fix heading to — +26 min
- Tue 8 Sept Max en route +20 min · last fix heading to — +20 min
- Thu 17 Sept Max en route +19 min · last fix heading to — +19 min
- Tue 18 Aug Max en route +10 min · last fix heading to — +10 min
- Fri 18 Sept Max en route +9 min · last fix heading to — +9 min
Distribution · 90 days
56 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 46% · 26
- 3–10 min 46% · 26
- 10–30 min 7% · 4
- 30+ min 0% · 0
On-time by weekday
- 38% M n=8
- 38% T n=8
- 25% W n=8
- 50% T n=8
- 38% F n=8
- 71% S n=7
- 67% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 56 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 |
|---|---|---|---|
| 20:57 | +2 min | +7 min | |
| 21:00 | ≈ +2 min | ≈ +7 min | |
| 21:05 / 21:06 | ≈ +3 min | ≈ +7 min | |
| 21:08 / 21:09 | ≈ +3 min | ≈ +8 min | |
| 21:14 | +3 min | +8 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 11 July 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 |
|---|---|---|---|
| Thu 5 Nov | Retz 21:14 | No data | — |
| Wed 4 Nov | Retz 21:14 | No data | — |
| Tue 3 Nov | Retz 21:14 | No data | — |
| Mon 2 Nov | Retz 21:14 | No data | — |
| Sun 1 Nov | Retz 21:14 | No data | — |
| Sat 31 Oct | Retz 21:15 | No data | — |
| Fri 30 Oct | Retz 21:15 | No data | — |
| Thu 29 Oct | Retz 21:15 | No data | — |
| Wed 28 Oct | Retz 21:15 | No data | — |
| Tue 27 Oct | Retz 21:16 | No data | — |
| Mon 26 Oct | Retz 21:15 | No data | — |
| Sun 25 Oct | Retz 21:15 | No data | — |
| Sat 24 Oct | Retz 21:15 | No data | — |
| Fri 23 Oct | Retz 21:15 | No data | — |
| Thu 22 Oct | Retz 21:15 | No data | — |
| Wed 21 Oct | Retz 21:15 | No data | — |
| Tue 20 Oct | Retz 21:15 | No data | — |
| Mon 19 Oct | Retz 21:16 | No data | — |
| Sun 18 Oct | Retz 21:15 | No data | — |
| Sat 17 Oct | Retz 21:15 | No data | — |
| Fri 16 Oct | Retz 21:15 | No data | — |
| Thu 15 Oct | Retz 21:15 | No data | — |
| Wed 14 Oct | Retz 21:15 | No data | — |
| Tue 13 Oct | Retz 21:15 | No data | — |
| Mon 12 Oct | Retz 21:16 | No data | — |
| Sun 11 Oct | Retz 21:15 | No data | — |
| Sat 10 Oct | Retz 21:15 | No data | — |
| Fri 9 Oct | Retz 21:15 | No data | — |
| Thu 8 Oct | Retz 21:15 | No data | — |
| Wed 7 Oct | Retz 21:15 | No data | — |