Os 20314 20314 Kralupy n.V. – Velvary
Alerts for train 20314
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 20314.
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 10: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 8 Oct Max en route +9 min · last fix heading to Velvary +7 min
- Mon 26 Oct Max en route +7 min · last fix heading to Velvary +6 min
- Mon 2 Nov Max en route +7 min · last fix heading to Velvary +5 min
- Fri 30 Oct Max en route +5 min · last fix heading to Velvary +5 min
- Thu 29 Oct Max en route +5 min · last fix heading to Velvary +5 min
Distribution · 90 days
61 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 79% · 48
- 3–10 min 21% · 13
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=12
- 100% T n=13
- 100% W n=12
- 58% T n=12
- 83% F n=12
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 61 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 |
|---|---|---|---|
| 10:26 | on time | +4 min | |
| 10:29 / 10:30 | ≈ on time | ≈ +4 min | |
| 10:35 | ≈ on time | ≈ +4 min | |
| 10:40 | ≈ on time | ≈ +5 min | |
| 10:46 | on time | +5 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 10:49 | +1 min | +3 min |
| Tue 3 Nov | Velvary 10:49 | 0 min | +2 min |
| Mon 2 Nov | Velvary 10:49 | +5 min | +7 min |
| Fri 30 Oct | Velvary 10:54 | +5 min | +5 min |
| Thu 29 Oct | Velvary 10:54 | +5 min | +5 min |
| Tue 27 Oct | Velvary 10:51 | 0 min | +3 min |
| Mon 26 Oct | Velvary 10:51 | +6 min | +7 min |
| Fri 23 Oct | Velvary 10:51 | 0 min | +2 min |
| Thu 22 Oct | Velvary 10:52 | +3 min | +3 min |
| Wed 21 Oct | Velvary 10:50 | 0 min | +3 min |
| Tue 20 Oct | Velvary 10:51 | +1 min | +2 min |
| Mon 19 Oct | Velvary 10:56 | +5 min | +8 min |
| Fri 16 Oct | Velvary 10:51 | 0 min | +2 min |
| Thu 15 Oct | Velvary 10:52 | +3 min | +3 min |
| Wed 14 Oct | Velvary 10:50 | 0 min | +1 min |
| Tue 13 Oct | Velvary 10:51 | +1 min | +4 min |
| Mon 12 Oct | Velvary 10:56 | +5 min | +8 min |
| Fri 9 Oct | Velvary 10:47 | +1 min | +2 min |
| Thu 8 Oct | Velvary 10:57 | +7 min | +9 min |
| Wed 7 Oct | Velvary 10:51 | 0 min | +2 min |
| Tue 6 Oct | Velvary 10:47 | 0 min | +4 min |
| Mon 5 Oct | — 11:00 | 0 min | +4 min |
| Fri 2 Oct | — 11:01 | 0 min | — |
| Thu 1 Oct | — 11:00 | 0 min | +2 min |
| Wed 30 Sept | — 11:00 | 0 min | — |
| Tue 29 Sept | — 11:00 | 0 min | — |
| Fri 25 Sept | — 11:00 | 0 min | — |
| Thu 24 Sept | — 11:02 | +1 min | +1 min |
| Wed 23 Sept | — 11:01 | 0 min | — |
| Tue 22 Sept | — 11:01 | 0 min | +3 min |