Os 27881 27881 Nezvěstice – Mirošov
Alerts for train 27881
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 27881.
It has not run yet today
Last recorded run: Saturday 7 November No data
Next service: today 21:33 from Nezvěstice · Sun 8 Nov
Last 30 days
Arrival delay at Mirošov, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 4 Oct Max en route +14 min · last fix heading to — +9 min
- Wed 16 Sept Max en route +9 min · last fix heading to — +9 min
- Sat 12 Sept Max en route +9 min · last fix heading to — +9 min
- Thu 24 Sept Max en route +8 min · last fix heading to — +8 min
- Wed 23 Sept Max en route +8 min · last fix heading to — +8 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 69% · 38
- 3–10 min 31% · 17
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 75% T n=8
- 50% W n=8
- 75% T n=8
- 63% F n=8
- 88% S n=8
- 63% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 55 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 |
|---|---|---|---|
| 21:33 | on time | +2 min | |
| 21:38 | ≈ on time | ≈ +2 min | |
| 21:42 | ≈ on time | ≈ +3 min | |
| 21:45 | ≈ on time | ≈ +3 min | |
| 21:48 | ≈ on time | ≈ +4 min | |
| 21:51 | ≈ on time | ≈ +5 min | |
| 21:56 / 21:57 | ≈ on time | ≈ +6 min | |
| 21:59 | ≈ on time | ≈ +7 min | |
| 22:02 | ≈ on time | ≈ +7 min | |
| 22:04 | on time | +8 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 |
|---|---|---|---|
| Sat 7 Nov | Mirošov 22:04 | No data | — |
| Fri 6 Nov | Mirošov 22:04 | No data | — |
| Thu 5 Nov | Mirošov 22:04 | No data | — |
| Wed 4 Nov | Mirošov 22:04 | No data | — |
| Tue 3 Nov | Mirošov 22:04 | No data | — |
| Mon 2 Nov | Mirošov 22:04 | No data | — |
| Sun 1 Nov | Mirošov 22:04 | No data | — |
| Sat 31 Oct | Mirošov 22:05 | No data | — |
| Fri 30 Oct | Mirošov 22:05 | No data | — |
| Thu 29 Oct | Mirošov 22:05 | No data | — |
| Wed 28 Oct | Mirošov 22:05 | No data | — |
| Tue 27 Oct | Mirošov 22:06 | No data | — |
| Mon 26 Oct | Mirošov 22:05 | No data | — |
| Sun 25 Oct | Mirošov 22:05 | No data | — |
| Sat 24 Oct | Mirošov 22:05 | No data | — |
| Fri 23 Oct | Mirošov 22:05 | No data | — |
| Thu 22 Oct | Mirošov 22:05 | No data | — |
| Wed 21 Oct | Mirošov 22:05 | No data | — |
| Tue 20 Oct | Mirošov 22:05 | No data | — |
| Mon 19 Oct | Mirošov 22:06 | No data | — |
| Sun 18 Oct | Mirošov 22:05 | No data | — |
| Sat 17 Oct | Mirošov 22:05 | No data | — |
| Fri 16 Oct | Mirošov 22:05 | No data | — |
| Thu 15 Oct | Mirošov 22:05 | No data | — |
| Wed 14 Oct | Mirošov 22:05 | No data | — |
| Tue 13 Oct | Mirošov 22:05 | No data | — |
| Mon 12 Oct | Mirošov 22:05 | No data | — |
| Sun 11 Oct | Mirošov 22:05 | No data | — |
| Sat 10 Oct | Mirošov 22:05 | No data | — |
| Fri 9 Oct | Mirošov 22:05 | No data | — |