Os 12733 12733 Rudoltice v Čechách – Lanškroun
Alerts for train 12733
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 12733.
It has not run yet today
Last recorded run: Friday 13 November No data
Next service: today 14:43 from Rudoltice v Čechách · Mon 16 Nov
Last 30 days
Arrival delay at Lanškroun, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 18 Sept Max en route +14 min · last fix heading to — +14 min
- Wed 23 Sept Max en route +13 min · last fix heading to — +13 min
- Thu 17 Sept Max en route +12 min · last fix heading to — +12 min
- Tue 15 Sept Max en route +11 min · last fix heading to — +11 min
- Fri 25 Sept Max en route +9 min · last fix heading to — +9 min
Distribution · 90 days
23 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 35% · 8
- 3–10 min 48% · 11
- 10–30 min 17% · 4
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 40% T n=5
- 40% W n=5
- 40% T n=5
- 0% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 23 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 |
|---|---|---|---|
| 14:43 | +5 min | +12 min | |
| 14:49 | +5 min | +12 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 |
|---|---|---|---|
| Fri 13 Nov | Lanškroun 14:49 | No data | — |
| Thu 12 Nov | Lanškroun 14:49 | No data | — |
| Wed 11 Nov | Lanškroun 14:49 | No data | — |
| Tue 10 Nov | Lanškroun 14:49 | No data | — |
| Mon 9 Nov | Lanškroun 14:49 | No data | — |
| Fri 6 Nov | Lanškroun 14:49 | No data | — |
| Thu 5 Nov | Lanškroun 14:49 | No data | — |
| Wed 4 Nov | Lanškroun 14:49 | No data | — |
| Tue 3 Nov | Lanškroun 14:49 | No data | — |
| Mon 2 Nov | Lanškroun 14:49 | No data | — |
| Fri 30 Oct | Lanškroun 14:50 | No data | — |
| Thu 29 Oct | Lanškroun 14:50 | No data | — |
| Tue 27 Oct | Lanškroun 14:50 | No data | — |
| Mon 26 Oct | Lanškroun 14:50 | No data | — |
| Fri 23 Oct | Lanškroun 14:50 | No data | — |
| Thu 22 Oct | Lanškroun 14:50 | No data | — |
| Wed 21 Oct | Lanškroun 14:50 | No data | — |
| Tue 20 Oct | Lanškroun 14:50 | No data | — |
| Mon 19 Oct | Lanškroun 14:50 | No data | — |
| Fri 16 Oct | Lanškroun 14:50 | No data | — |
| Thu 15 Oct | Lanškroun 14:50 | No data | — |
| Wed 14 Oct | Lanškroun 14:50 | No data | — |
| Tue 13 Oct | Lanškroun 14:50 | No data | — |
| Mon 12 Oct | Lanškroun 14:50 | No data | — |
| Fri 9 Oct | Lanškroun 14:50 | No data | — |
| Thu 8 Oct | Lanškroun 14:50 | No data | — |
| Wed 7 Oct | Lanškroun 14:50 | No data | — |
| Tue 6 Oct | Lanškroun 14:50 | No data | — |
| Mon 5 Oct | — 15:04 | +1 min | +2 min |
| Fri 2 Oct | — 15:09 | +6 min | +8 min |