Os 3472 3472 Opava východ – Krnov
Alerts for train 3472
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 3472.
✓ Today’s run finished
Today, last fix heading to Krnov at 17:34 No data
- Opava východ16:56
- Opava západ17:00
- Vávrovice17:06
- Skrochovice17:15
- Úvalno17:22
- Krnov-Cvilín17:28
- Krnov17:33
Next service: tomorrow 16:56 from Opava východ · Tue 10 Nov
Last 30 days
Arrival delay at Krnov, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 21 Sept Max en route +16 min · last fix heading to — +13 min
- Fri 25 Sept Max en route +7 min · last fix heading to — +7 min
- Tue 22 Sept Max en route +9 min · last fix heading to — +7 min
- Fri 2 Oct Max en route +9 min · last fix heading to — +6 min
- Wed 9 Sept Max en route +9 min · last fix heading to — +6 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 61% · 14
- 3–10 min 35% · 8
- 10–30 min 4% · 1
- 30+ min 0% · 0
On-time by weekday
- 67% M n=3
- 80% T n=5
- 60% W n=5
- 80% T n=5
- 20% F n=5
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 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 |
|---|---|---|---|
| 16:56 | on time | on time | |
| 17:00 / 17:01 | ≈ on time | ≈ +1 min | |
| 17:06 | ≈ on time | ≈ +2 min | |
| 17:11 / 17:12 | ≈ on time | ≈ +3 min | |
| 17:15 / 17:18 | ≈ on time | ≈ +4 min | |
| 17:22 / 17:23 | ≈ on time | ≈ +5 min | |
| 17:28 / 17:29 | ≈ on time | ≈ +6 min | |
| 17:33 | on time | +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 |
|---|---|---|---|
| Mon 9 Nov | Krnov 17:34 | No data | — |
| Fri 6 Nov | Krnov 17:34 | No data | — |
| Thu 5 Nov | Krnov 17:34 | No data | — |
| Wed 4 Nov | Krnov 17:34 | No data | — |
| Tue 3 Nov | Krnov 17:34 | No data | — |
| Mon 2 Nov | Krnov 17:34 | No data | — |
| Fri 30 Oct | Krnov 17:34 | No data | — |
| Thu 29 Oct | Krnov 17:34 | No data | — |
| Tue 27 Oct | Krnov 17:34 | No data | — |
| Mon 26 Oct | Krnov 17:34 | No data | — |
| Fri 23 Oct | Krnov 17:35 | No data | — |
| Thu 22 Oct | Krnov 17:34 | No data | — |
| Wed 21 Oct | Krnov 17:34 | No data | — |
| Tue 20 Oct | Krnov 17:35 | No data | — |
| Mon 19 Oct | Krnov 17:34 | No data | — |
| Fri 16 Oct | Krnov 17:34 | No data | — |
| Thu 15 Oct | Krnov 17:34 | No data | — |
| Wed 14 Oct | Krnov 17:34 | No data | — |
| Tue 13 Oct | Krnov 17:34 | No data | — |
| Mon 12 Oct | Krnov 17:35 | No data | — |
| Fri 9 Oct | Krnov 17:34 | No data | — |
| Thu 8 Oct | Krnov 17:34 | No data | — |
| Wed 7 Oct | Krnov 17:34 | No data | — |
| Tue 6 Oct | Krnov 17:34 | No data | — |
| Mon 5 Oct | Krnov 17:34 | No data | — |
| Fri 2 Oct | — 17:53 | +6 min | +9 min |
| Thu 1 Oct | — 17:48 | +1 min | +5 min |
| Wed 30 Sept | — 17:48 | 0 min | +2 min |
| Tue 29 Sept | — 17:48 | 0 min | — |
| Fri 25 Sept | — 17:55 | +7 min | +7 min |