Os 3768 3768 Zábřeh na Moravě – Rudoltice v Čechách
Alerts for train 3768
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 3768.
✓ Today’s run finished
Today, last fix heading to Rudoltice v Čechách at 05:29 No data
- Zábřeh na Moravě05:02
- Hoštejn05:10
- Hoštejn05:14
- Krasíkov05:19
- Krasíkov05:21
- Luková u Rudoltic v Čechách05:26
- Rudoltice v Čechách05:29
Next service: Tuesday 05:02 from Zábřeh na Moravě · Tue 17 Nov
Last 30 days
Arrival delay at Rudoltice v Čechách, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 29 Aug Max en route +7 min · last fix heading to — +7 min
- Sat 22 Aug Max en route +7 min · last fix heading to — +7 min
- Sat 12 Sept Max en route +10 min · last fix heading to — +6 min
- Sat 3 Oct Max en route +6 min · last fix heading to — +5 min
- Sat 26 Sept Max en route +4 min · last fix heading to — +4 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 40% · 6
- 3–10 min 60% · 9
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- 0% S n=7
- 71% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 15 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 |
|---|---|---|---|
| 05:02 | on time | +3 min | |
| 05:05 | ≈ on time | ≈ +3 min | |
| 05:10 / 05:13 | ≈ +1 min | ≈ +3 min | |
| 05:14 | ≈ +2 min | ≈ +3 min | |
| 05:17 | ≈ +2 min | ≈ +4 min | |
| 05:19 / 05:20 | ≈ +3 min | ≈ +4 min | |
| 05:21 | ≈ +3 min | ≈ +5 min | |
| 05:23 | ≈ +3 min | ≈ +5 min | |
| 05:26 | ≈ +4 min | ≈ +6 min | |
| 05:29 | +4 min | +7 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 |
|---|---|---|---|
| Sun 15 Nov | Rudoltice v Čechách 05:29 | No data | — |
| Sat 14 Nov | Rudoltice v Čechách 05:29 | No data | — |
| Sun 8 Nov | Rudoltice v Čechách 05:29 | No data | — |
| Sat 7 Nov | Rudoltice v Čechách 05:29 | No data | — |
| Sun 1 Nov | Rudoltice v Čechách 05:31 | No data | — |
| Sat 31 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Wed 28 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sun 25 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sat 24 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sun 18 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sat 17 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sun 11 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sat 10 Oct | Rudoltice v Čechách 05:31 | No data | — |
| Sun 4 Oct | — 05:44 | 0 min | — |
| Sat 3 Oct | — 05:49 | +5 min | +6 min |
| Mon 28 Sept | — 05:47 | +2 min | +2 min |
| Sun 27 Sept | — 05:46 | +1 min | +1 min |
| Sat 26 Sept | — 05:48 | +4 min | +4 min |
| Sun 20 Sept | — 05:46 | +3 min | +3 min |
| Sat 19 Sept | — 05:49 | +4 min | +4 min |
| Sun 13 Sept | — 05:45 | +2 min | +3 min |
| Sat 12 Sept | — 05:51 | +6 min | +10 min |
| Sun 6 Sept | — 05:44 | 0 min | — |
| Sat 5 Sept | — 05:49 | +4 min | +4 min |
| Sun 30 Aug | — 05:43 | 0 min | +3 min |
| Sat 29 Aug | — 05:52 | +7 min | +7 min |
| Sun 23 Aug | — 05:47 | +4 min | +4 min |
| Sat 22 Aug | — 05:50 | +7 min | +7 min |