Os 27132 27132 Chodov – Loket
Alerts for train 27132
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 27132.
It has not run yet today
Last recorded run: Saturday 7 November No data
Next service: today 19:22 from Chodov · Sun 8 Nov
Last 30 days
Arrival delay at Loket, 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 23 Aug Max en route +7 min · last fix heading to — +6 min
- Sun 20 Sept Max en route +4 min · last fix heading to — +4 min
- Sat 22 Aug Max en route +6 min · last fix heading to — +4 min
- Sat 26 Sept Max en route +3 min · last fix heading to — +3 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 93% · 51
- 3–10 min 7% · 4
- 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
- 75% S n=8
- 75% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 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 |
|---|---|---|---|
| 19:22 | on time | +2 min | |
| 19:25 / 19:26 | ≈ on time | ≈ +2 min | |
| 19:28 | ≈ on time | ≈ +2 min | |
| 19:33 | on time | +2 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 | Loket 19:34 | No data | — |
| Fri 6 Nov | Loket 19:34 | No data | — |
| Thu 5 Nov | Loket 19:34 | No data | — |
| Wed 4 Nov | Loket 19:34 | No data | — |
| Tue 3 Nov | Loket 19:34 | No data | — |
| Mon 2 Nov | Loket 19:34 | No data | — |
| Sun 1 Nov | Loket 19:34 | No data | — |
| Sat 31 Oct | Loket 19:34 | No data | — |
| Fri 30 Oct | Loket 19:34 | No data | — |
| Thu 29 Oct | Loket 19:34 | No data | — |
| Wed 28 Oct | Loket 19:34 | No data | — |
| Tue 27 Oct | Loket 19:35 | No data | — |
| Mon 26 Oct | Loket 19:34 | No data | — |
| Sun 25 Oct | Loket 19:34 | No data | — |
| Sat 24 Oct | Loket 19:34 | No data | — |
| Fri 23 Oct | Loket 19:34 | No data | — |
| Thu 22 Oct | Loket 19:34 | No data | — |
| Wed 21 Oct | Loket 19:34 | No data | — |
| Tue 20 Oct | Loket 19:34 | No data | — |
| Mon 19 Oct | Loket 19:34 | No data | — |
| Sun 18 Oct | Loket 19:34 | No data | — |
| Sat 17 Oct | Loket 19:34 | No data | — |
| Fri 16 Oct | Loket 19:34 | No data | — |
| Thu 15 Oct | Loket 19:34 | No data | — |
| Wed 14 Oct | Loket 19:34 | No data | — |
| Tue 13 Oct | Loket 19:34 | No data | — |
| Mon 12 Oct | Loket 19:35 | No data | — |
| Sun 11 Oct | Loket 19:34 | No data | — |
| Sat 10 Oct | Loket 19:34 | No data | — |
| Fri 9 Oct | Loket 19:34 | No data | — |