Os 20326 20326 Kralupy n.V. – Velvary
Alerts for train 20326
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 20326.
It has not run yet today
Last recorded run: Wednesday 4 November +3 min
Next service: today 16:26 from Kralupy n.V. · Thu 5 Nov
Last 30 days
Arrival delay at Velvary, 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 +63 min · last fix heading to — +63 min
- Fri 23 Oct Max en route +14 min · last fix heading to Velvary +10 min
- Tue 18 Aug Max en route +10 min · last fix heading to — +10 min
- Wed 21 Oct Max en route +10 min · last fix heading to Velvary +9 min
- Wed 12 Aug Max en route +10 min · last fix heading to — +9 min
Distribution · 90 days
89 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 62% · 55
- 3–10 min 35% · 31
- 10–30 min 2% · 2
- 30+ min 1% · 1
On-time by weekday
- 69% M n=13
- 38% T n=13
- 46% W n=13
- 67% T n=12
- 75% F n=12
- 62% S n=13
- 77% S n=13
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 89 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:26 | +1 min | +7 min | |
| 16:29 / 16:30 | ≈ +1 min | ≈ +7 min | |
| 16:35 | ≈ +2 min | ≈ +7 min | |
| 16:39 | ≈ +1 min | ≈ +6 min | |
| 16:45 | +1 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 |
|---|---|---|---|
| Wed 4 Nov | Velvary 16:49 | +3 min | +3 min |
| Tue 3 Nov | Velvary 16:49 | +3 min | +3 min |
| Mon 2 Nov | Velvary 16:49 | +5 min | +6 min |
| Sun 1 Nov | Velvary 16:51 | +2 min | +5 min |
| Sat 31 Oct | Velvary 16:50 | +6 min | +6 min |
| Fri 30 Oct | Velvary 16:49 | 0 min | +1 min |
| Thu 29 Oct | Velvary 16:51 | +2 min | +3 min |
| Wed 28 Oct | Velvary 16:54 | +6 min | +6 min |
| Tue 27 Oct | Velvary 16:50 | +5 min | +5 min |
| Mon 26 Oct | Velvary 16:47 | +2 min | +3 min |
| Sun 25 Oct | Velvary 16:52 | +2 min | +3 min |
| Sat 24 Oct | Velvary 16:52 | +3 min | +3 min |
| Fri 23 Oct | Velvary 16:59 | +10 min | +14 min |
| Thu 22 Oct | Velvary 16:46 | +1 min | +2 min |
| Wed 21 Oct | Velvary 16:58 | +9 min | +10 min |
| Tue 20 Oct | Velvary 16:50 | 0 min | — |
| Mon 19 Oct | Velvary 16:50 | 0 min | +1 min |
| Sun 18 Oct | Velvary 16:49 | +1 min | +1 min |
| Sat 17 Oct | Velvary 16:51 | +7 min | +7 min |
| Fri 16 Oct | Velvary 16:49 | +1 min | +1 min |
| Thu 15 Oct | Velvary 16:52 | +3 min | +3 min |
| Wed 14 Oct | Velvary 16:46 | +1 min | +3 min |
| Tue 13 Oct | Velvary 16:52 | +2 min | +4 min |
| Mon 12 Oct | Velvary 16:51 | +5 min | +7 min |
| Sun 11 Oct | Velvary 16:49 | 0 min | +1 min |
| Sat 10 Oct | Velvary 16:51 | +4 min | +4 min |
| Fri 9 Oct | Velvary 16:47 | 0 min | +2 min |
| Thu 8 Oct | Velvary 16:53 | +4 min | +5 min |
| Wed 7 Oct | Velvary 16:50 | +1 min | +2 min |
| Tue 6 Oct | Velvary 16:49 | +2 min | +2 min |