Os 27112 27112 Nová Role – Loket
Alerts for train 27112
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 27112.
✓ Today’s run finished
Today, last fix heading to Loket at 15:33 No data
- Nová Role14:57
- Božičany15:01
- Mírová15:04
- Chodov15:12
- Nové Sedlo u Lokte15:24
- Loučky15:27
- Loket15:32
Next service: tomorrow 14:57 from Nová Role · Fri 6 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
- Mon 28 Sept Max en route +11 min · last fix heading to — +10 min
- Tue 18 Aug Max en route +11 min · last fix heading to — +10 min
- Thu 24 Sept Max en route +5 min · last fix heading to — +5 min
- Sun 13 Sept Max en route +5 min · last fix heading to — +5 min
- Sat 29 Aug Max en route +6 min · last fix heading to — +5 min
Distribution · 90 days
59 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 47
- 3–10 min 17% · 10
- 10–30 min 3% · 2
- 30+ min 0% · 0
On-time by weekday
- 89% M n=9
- 75% T n=8
- 75% W n=8
- 88% T n=8
- 75% F n=8
- 78% S n=9
- 78% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (7 stops).
Last 90 days, 59 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 |
|---|---|---|---|
| 14:57 | on time | +3 min | |
| 15:01 | ≈ on time | ≈ +3 min | |
| 15:04 | ≈ on time | ≈ +3 min | |
| 15:12 / 15:21 | ≈ on time | ≈ +3 min | |
| 15:24 / 15:25 | ≈ +1 min | ≈ +4 min | |
| 15:27 | ≈ +1 min | ≈ +4 min | |
| 15:32 | +1 min | +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 |
|---|---|---|---|
| Thu 5 Nov | Loket 15:33 | No data | — |
| Wed 4 Nov | Loket 15:34 | No data | — |
| Tue 3 Nov | Loket 15:33 | No data | — |
| Mon 2 Nov | Loket 15:33 | No data | — |
| Sun 1 Nov | Loket 15:33 | No data | — |
| Sat 31 Oct | Loket 15:33 | No data | — |
| Fri 30 Oct | Loket 15:33 | No data | — |
| Thu 29 Oct | Loket 15:33 | No data | — |
| Wed 28 Oct | Loket 15:33 | No data | — |
| Tue 27 Oct | Loket 15:33 | No data | — |
| Mon 26 Oct | Loket 15:33 | No data | — |
| Sun 25 Oct | Loket 15:33 | No data | — |
| Sat 24 Oct | Loket 15:33 | No data | — |
| Fri 23 Oct | Loket 15:33 | No data | — |
| Thu 22 Oct | Loket 15:33 | No data | — |
| Wed 21 Oct | Loket 15:33 | No data | — |
| Tue 20 Oct | Loket 15:33 | No data | — |
| Mon 19 Oct | Loket 15:33 | No data | — |
| Sun 18 Oct | Loket 15:33 | No data | — |
| Sat 17 Oct | Loket 15:33 | No data | — |
| Fri 16 Oct | Loket 15:33 | No data | — |
| Thu 15 Oct | Loket 15:33 | No data | — |
| Wed 14 Oct | Loket 15:33 | No data | — |
| Tue 13 Oct | Loket 15:33 | No data | — |
| Mon 12 Oct | Loket 15:33 | No data | — |
| Sun 11 Oct | Loket 15:33 | No data | — |
| Sat 10 Oct | Loket 15:33 | No data | — |
| Fri 9 Oct | Loket 15:33 | No data | — |
| Thu 8 Oct | Loket 15:33 | No data | — |
| Wed 7 Oct | Loket 15:33 | No data | — |