Os 27122 27122 Chodov – Loket
Alerts for train 27122
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 27122.
✓ Today’s run finished
Today, last fix heading to Loket at 09:34 No data
- Chodov09:22
- Nové Sedlo u Lokte09:25
- Loučky09:28
- Loket09:33
Next service: tomorrow 09:22 from Chodov · Sat 7 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
- Thu 20 Aug Max en route +13 min · last fix heading to — +13 min
- Sat 12 Sept Max en route +11 min · last fix heading to — +11 min
- Mon 24 Aug Max en route +11 min · last fix heading to — +11 min
- Sun 23 Aug Max en route +7 min · last fix heading to — +7 min
- Tue 15 Sept Max en route +7 min · last fix heading to — +6 min
Distribution · 90 days
58 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 83% · 48
- 3–10 min 12% · 7
- 10–30 min 5% · 3
- 30+ min 0% · 0
On-time by weekday
- 78% M n=9
- 63% T n=8
- 100% W n=8
- 88% T n=8
- 100% F n=8
- 63% S n=8
- 89% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 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 |
|---|---|---|---|
| 09:22 | on time | +4 min | |
| 09:25 / 09:26 | ≈ on time | ≈ +5 min | |
| 09:28 | ≈ +1 min | ≈ +4 min | |
| 09:33 | on time | +4 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 | Loket 09:34 | No data | — |
| Thu 5 Nov | Loket 09:34 | No data | — |
| Wed 4 Nov | Loket 09:34 | No data | — |
| Tue 3 Nov | Loket 09:34 | No data | — |
| Mon 2 Nov | Loket 09:34 | No data | — |
| Sun 1 Nov | Loket 09:34 | No data | — |
| Sat 31 Oct | Loket 09:34 | No data | — |
| Fri 30 Oct | Loket 09:34 | No data | — |
| Thu 29 Oct | Loket 09:34 | No data | — |
| Wed 28 Oct | Loket 09:34 | No data | — |
| Tue 27 Oct | Loket 09:35 | No data | — |
| Mon 26 Oct | Loket 09:34 | No data | — |
| Sun 25 Oct | Loket 09:34 | No data | — |
| Sat 24 Oct | Loket 09:34 | No data | — |
| Fri 23 Oct | Loket 09:35 | No data | — |
| Thu 22 Oct | Loket 09:35 | No data | — |
| Wed 21 Oct | Loket 09:34 | No data | — |
| Tue 20 Oct | Loket 09:34 | No data | — |
| Mon 19 Oct | Loket 09:34 | No data | — |
| Sun 18 Oct | Loket 09:34 | No data | — |
| Sat 17 Oct | Loket 09:34 | No data | — |
| Fri 16 Oct | Loket 09:34 | No data | — |
| Thu 15 Oct | Loket 09:34 | No data | — |
| Wed 14 Oct | Loket 09:34 | No data | — |
| Tue 13 Oct | Loket 09:34 | No data | — |
| Mon 12 Oct | Loket 09:34 | No data | — |
| Sun 11 Oct | Loket 09:34 | No data | — |
| Sat 10 Oct | Loket 09:34 | No data | — |
| Fri 9 Oct | Loket 09:34 | No data | — |
| Thu 8 Oct | Loket 09:34 | No data | — |