Os 18014 18014 Číčenice – Volary
Alerts for train 18014
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 18014.
It has not run yet today
Last recorded run: Wednesday 4 November No data
Next service: today 19:38 from Číčenice · Thu 5 Nov
Last 30 days
Arrival delay at Volary, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 21 Aug Max en route +32 min · last fix heading to — +32 min
- Mon 31 Aug Max en route +20 min · last fix heading to — +13 min
- Thu 13 Aug Max en route +24 min · last fix heading to — +11 min
- Fri 28 Aug Max en route +13 min · last fix heading to — +10 min
- Wed 9 Sept Max en route +20 min · last fix heading to — +9 min
Distribution · 90 days
58 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 21% · 12
- On time 59% · 34
- 3–10 min 14% · 8
- 10–30 min 5% · 3
- 30+ min 2% · 1
On-time by weekday
- 63% M n=8
- 75% T n=8
- 88% W n=8
- 75% T n=8
- 75% F n=8
- 100% S n=9
- 78% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (17 stops).
Last 90 days, 58 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 |
|---|---|---|---|
| 19:38 | +6 min | +15 min | |
| 19:43 / 19:44 | ≈ +6 min | ≈ +15 min | |
| 19:47 | ≈ +5 min | ≈ +14 min | |
| 19:52 | ≈ +5 min | ≈ +14 min | |
| 19:55 / 19:57 | ≈ +5 min | ≈ +14 min | |
| 20:03 | ≈ +4 min | ≈ +13 min | |
| 20:06 / 20:07 | ≈ +4 min | ≈ +13 min | |
| 20:14 | ≈ +3 min | ≈ +12 min | |
| 20:19 / 20:24 | ≈ +3 min | ≈ +12 min | |
| 20:27 | ≈ +2 min | ≈ +11 min | |
| 20:33 | ≈ +2 min | ≈ +10 min | |
| 20:37 / 20:38 | ≈ +1 min | ≈ +10 min | |
| 20:41 | ≈ +1 min | ≈ +9 min | |
| 20:46 | ≈ +1 min | ≈ +8 min | |
| 20:50 / 20:51 | ≈ on time | ≈ +8 min | |
| 20:54 | ≈ on time | ≈ +7 min | |
| 21:06 | on time | +6 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 | Volary 21:07 | No data | — |
| Tue 3 Nov | Volary 21:07 | No data | — |
| Mon 2 Nov | Volary 21:07 | No data | — |
| Sun 1 Nov | Volary 21:07 | No data | — |
| Sat 31 Oct | Volary 21:07 | No data | — |
| Fri 30 Oct | Volary 21:07 | No data | — |
| Thu 29 Oct | Volary 21:07 | No data | — |
| Wed 28 Oct | Volary 21:07 | No data | — |
| Tue 27 Oct | Volary 21:08 | No data | — |
| Mon 26 Oct | Volary 21:07 | No data | — |
| Sun 25 Oct | Volary 21:08 | No data | — |
| Sat 24 Oct | Volary 21:07 | No data | — |
| Fri 23 Oct | Volary 21:07 | No data | — |
| Thu 22 Oct | Volary 21:07 | No data | — |
| Wed 21 Oct | Volary 21:07 | No data | — |
| Tue 20 Oct | Volary 21:07 | No data | — |
| Mon 19 Oct | Volary 21:08 | No data | — |
| Sun 18 Oct | Volary 21:07 | No data | — |
| Sat 17 Oct | Volary 21:07 | No data | — |
| Fri 16 Oct | Volary 21:07 | No data | — |
| Thu 15 Oct | Volary 21:07 | No data | — |
| Wed 14 Oct | Volary 21:07 | No data | — |
| Tue 13 Oct | Volary 21:07 | No data | — |
| Mon 12 Oct | Volary 21:08 | No data | — |
| Sun 11 Oct | Volary 21:07 | No data | — |
| Sat 10 Oct | Volary 21:07 | No data | — |
| Fri 9 Oct | Volary 21:07 | No data | — |
| Thu 8 Oct | Volary 21:08 | No data | — |
| Wed 7 Oct | Volary 21:07 | No data | — |
| Tue 6 Oct | Volary 21:07 | No data | — |