Os 18000 18000 Číčenice – Volary
Alerts for train 18000
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 18000.
It does not run today
Last recorded run: Friday 6 November No data
Next service: tomorrow 05:38 from Číčenice · Mon 9 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
Distribution · 90 days
39 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 18% · 7
- On time 82% · 32
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 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 (17 stops).
Last 90 days, 39 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 |
|---|---|---|---|
| 05:38 | on time | +1 min | |
| 05:43 / 05:44 | ≈ on time | ≈ +1 min | |
| 05:47 | ≈ on time | ≈ +1 min | |
| 05:52 | ≈ on time | ≈ +1 min | |
| 05:55 / 05:57 | ≈ on time | ≈ +1 min | |
| 06:03 | ≈ on time | ≈ +1 min | |
| 06:06 / 06:07 | ≈ on time | ≈ on time | |
| 06:14 | ≈ on time | ≈ on time | |
| 06:19 / 06:29 | ≈ on time | ≈ on time | |
| 06:32 | ≈ 1 min early | ≈ on time | |
| 06:38 | ≈ 1 min early | ≈ on time | |
| 06:42 / 06:43 | ≈ 1 min early | ≈ on time | |
| 06:46 | ≈ 1 min early | ≈ on time | |
| 06:50 | ≈ 1 min early | ≈ on time | |
| 06:55 / 06:58 | ≈ 1 min early | ≈ on time | |
| 07:00 | ≈ 1 min early | ≈ on time | |
| 07:13 | 1 min early | on time |
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 | Volary 07:14 | No data | — |
| Thu 5 Nov | Volary 07:14 | No data | — |
| Wed 4 Nov | Volary 07:14 | No data | — |
| Tue 3 Nov | Volary 07:14 | No data | — |
| Mon 2 Nov | Volary 07:14 | No data | — |
| Fri 30 Oct | Volary 07:14 | No data | — |
| Thu 29 Oct | Volary 07:14 | No data | — |
| Tue 27 Oct | Volary 07:14 | No data | — |
| Mon 26 Oct | Volary 07:14 | No data | — |
| Fri 23 Oct | Volary 07:14 | No data | — |
| Thu 22 Oct | Volary 07:14 | No data | — |
| Wed 21 Oct | Volary 07:14 | No data | — |
| Tue 20 Oct | Volary 07:14 | No data | — |
| Mon 19 Oct | Volary 07:14 | No data | — |
| Fri 16 Oct | Volary 07:14 | No data | — |
| Thu 15 Oct | Volary 07:14 | No data | — |
| Wed 14 Oct | Volary 07:14 | No data | — |
| Tue 13 Oct | Volary 07:14 | No data | — |
| Mon 12 Oct | Volary 07:14 | No data | — |
| Fri 9 Oct | Volary 07:14 | No data | — |
| Thu 8 Oct | Volary 07:14 | No data | — |
| Wed 7 Oct | Volary 07:14 | No data | — |
| Tue 6 Oct | Volary 07:14 | No data | — |
| Mon 5 Oct | — 07:28 | 0 min | +2 min |
| Fri 2 Oct | — 07:27 | −1 min | — |
| Thu 1 Oct | — 07:27 | −1 min | — |
| Wed 30 Sept | — 07:26 | −1 min | — |
| Tue 29 Sept | — 07:25 | −2 min | +1 min |
| Fri 25 Sept | — 07:27 | 0 min | +5 min |
| Thu 24 Sept | — 07:26 | −1 min | +1 min |