Os 3652 3652 Hanušovice – Šumperk
Alerts for train 3652
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 3652.
✓ Today’s run finished
Today, last fix heading to Šumperk at 06:42 No data
- Hanušovice06:01
- Raškov06:06
- Bohdíkov06:08
- Ruda nad Moravou06:15
- Bohutín06:22
- Bludov lázně06:25
- Šumperk06:41
Next service: Monday 06:01 from Hanušovice · Mon 9 Nov
Last 30 days
Arrival delay at Šumperk, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 3% · 1
- On time 98% · 39
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 100% T n=8
- 100% W n=8
- 100% T n=8
- 100% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 40 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 |
|---|---|---|---|
| 06:01 | on time | on time | |
| 06:03 | ≈ on time | ≈ on time | |
| 06:06 | ≈ on time | ≈ on time | |
| 06:08 / 06:09 | ≈ on time | ≈ on time | |
| 06:12 | ≈ on time | ≈ +1 min | |
| 06:15 / 06:16 | ≈ on time | ≈ +1 min | |
| 06:19 | ≈ on time | ≈ +1 min | |
| 06:22 | ≈ on time | ≈ +1 min | |
| 06:25 | ≈ on time | ≈ +1 min | |
| 06:29 / 06:35 | ≈ on time | ≈ +1 min | |
| 06:41 | 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 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 6 Nov | Šumperk 06:42 | No data | — |
| Thu 5 Nov | Šumperk 06:42 | No data | — |
| Wed 4 Nov | Šumperk 06:42 | No data | — |
| Tue 3 Nov | Šumperk 06:42 | No data | — |
| Mon 2 Nov | Šumperk 06:42 | No data | — |
| Fri 30 Oct | Šumperk 06:42 | No data | — |
| Thu 29 Oct | Šumperk 06:42 | No data | — |
| Tue 27 Oct | Šumperk 06:42 | No data | — |
| Mon 26 Oct | Šumperk 06:42 | No data | — |
| Fri 23 Oct | Šumperk 06:42 | No data | — |
| Thu 22 Oct | Šumperk 06:42 | No data | — |
| Wed 21 Oct | Šumperk 06:42 | No data | — |
| Tue 20 Oct | Šumperk 06:42 | No data | — |
| Mon 19 Oct | Šumperk 06:42 | No data | — |
| Fri 16 Oct | Šumperk 06:42 | No data | — |
| Thu 15 Oct | Šumperk 06:42 | No data | — |
| Wed 14 Oct | Šumperk 06:42 | No data | — |
| Tue 13 Oct | Šumperk 06:42 | No data | — |
| Mon 12 Oct | Šumperk 06:42 | No data | — |
| Fri 9 Oct | Šumperk 06:42 | No data | — |
| Thu 8 Oct | Šumperk 06:42 | No data | — |
| Wed 7 Oct | Šumperk 06:42 | No data | — |
| Tue 6 Oct | Šumperk 06:42 | No data | — |
| Mon 5 Oct | — 06:58 | +2 min | +2 min |
| Fri 2 Oct | — 06:57 | +1 min | +1 min |
| Thu 1 Oct | — 06:56 | 0 min | — |
| Wed 30 Sept | — 06:55 | 0 min | — |
| Tue 29 Sept | — 06:55 | 0 min | +3 min |
| Fri 25 Sept | — 06:55 | 0 min | — |
| Thu 24 Sept | — 06:55 | 0 min | — |