Os 27862 27862 Příkosice – Nezvěstice
Alerts for train 27862
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 27862.
It does not run today
Last recorded run: Friday 6 November No data
Next service: Monday 06:02 from Příkosice · Mon 9 Nov
Last 30 days
Arrival delay at Nezvěstice, 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 25 Sept Max en route +7 min · last fix heading to — +7 min
- Mon 21 Sept Max en route +7 min · last fix heading to — +7 min
- Wed 16 Sept Max en route +7 min · last fix heading to — +7 min
- Tue 15 Sept Max en route +7 min · last fix heading to — +7 min
- Thu 24 Sept Max en route +6 min · last fix heading to — +6 min
Distribution · 90 days
40 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 13% · 5
- On time 53% · 21
- 3–10 min 35% · 14
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 63% T n=8
- 63% W n=8
- 63% T n=8
- 63% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 40 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 |
|---|---|---|---|
| 06:02 | on time | +1 min | |
| 06:05 | ≈ on time | ≈ +2 min | |
| 06:09 | ≈ on time | ≈ +2 min | |
| 06:12 | ≈ on time | ≈ +3 min | |
| 06:15 | ≈ 1 min early | ≈ +4 min | |
| 06:19 | ≈ 1 min early | ≈ +5 min | |
| 06:25 | 1 min early | +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 |
|---|---|---|---|
| Fri 6 Nov | Nezvěstice 06:24 | No data | — |
| Thu 5 Nov | Nezvěstice 06:24 | No data | — |
| Wed 4 Nov | Nezvěstice 06:24 | No data | — |
| Tue 3 Nov | Nezvěstice 06:25 | No data | — |
| Mon 2 Nov | Nezvěstice 06:24 | No data | — |
| Fri 30 Oct | Nezvěstice 06:26 | No data | — |
| Thu 29 Oct | Nezvěstice 06:26 | No data | — |
| Tue 27 Oct | Nezvěstice 06:26 | No data | — |
| Mon 26 Oct | Nezvěstice 06:26 | No data | — |
| Fri 23 Oct | Nezvěstice 06:27 | No data | — |
| Thu 22 Oct | Nezvěstice 06:26 | No data | — |
| Wed 21 Oct | Nezvěstice 06:26 | No data | — |
| Tue 20 Oct | Nezvěstice 06:26 | No data | — |
| Mon 19 Oct | Nezvěstice 06:26 | No data | — |
| Fri 16 Oct | Nezvěstice 06:26 | No data | — |
| Thu 15 Oct | Nezvěstice 06:26 | No data | — |
| Wed 14 Oct | Nezvěstice 06:26 | No data | — |
| Tue 13 Oct | Nezvěstice 06:26 | No data | — |
| Mon 12 Oct | Nezvěstice 06:26 | No data | — |
| Fri 9 Oct | Nezvěstice 06:26 | No data | — |
| Thu 8 Oct | Nezvěstice 06:26 | No data | — |
| Wed 7 Oct | Nezvěstice 06:26 | No data | — |
| Tue 6 Oct | Nezvěstice 06:27 | No data | — |
| Mon 5 Oct | — 06:39 | −1 min | — |
| Fri 2 Oct | — 06:39 | −1 min | — |
| Thu 1 Oct | — 06:39 | −1 min | — |
| Wed 30 Sept | — 06:37 | −2 min | — |
| Tue 29 Sept | — 06:39 | 0 min | — |
| Fri 25 Sept | — 06:47 | +7 min | +7 min |
| Thu 24 Sept | — 06:45 | +6 min | +6 min |