Os 26703 26703 Postoloprty – Louny
Alerts for train 26703
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 26703.
It has not run yet today
Last recorded run: Friday 6 November No data
Next service: today 09:41 from Postoloprty · Mon 9 Nov
Last 30 days
Arrival delay at Louny, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Tue 22 Sept Max en route +8 min · last fix heading to — +8 min
- Fri 28 Aug Max en route +9 min · last fix heading to — +8 min
- Wed 30 Sept Max en route +8 min · last fix heading to — +7 min
- Mon 14 Sept Max en route +9 min · last fix heading to — +7 min
- Tue 15 Sept Max en route +5 min · last fix heading to — +5 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 82% · 31
- 3–10 min 18% · 7
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 86% M n=7
- 71% T n=7
- 75% W n=8
- 88% T n=8
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 38 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:41 | on time | +2 min | |
| 09:45 | ≈ on time | ≈ +3 min | |
| 09:52 | ≈ on time | ≈ +5 min | |
| 09:54 | ≈ on time | ≈ +5 min | |
| 09:57 | on time | +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 | Louny 09:58 | No data | — |
| Thu 5 Nov | Louny 09:58 | No data | — |
| Wed 4 Nov | Louny 09:58 | No data | — |
| Tue 3 Nov | Louny 09:58 | No data | — |
| Mon 2 Nov | Louny 09:58 | No data | — |
| Fri 30 Oct | Louny 09:58 | No data | — |
| Thu 29 Oct | Louny 09:58 | No data | — |
| Tue 27 Oct | Louny 09:59 | No data | — |
| Mon 26 Oct | Louny 09:58 | No data | — |
| Fri 23 Oct | Louny 09:59 | No data | — |
| Thu 22 Oct | Louny 09:59 | No data | — |
| Wed 21 Oct | Louny 09:58 | No data | — |
| Tue 20 Oct | Louny 09:58 | No data | — |
| Mon 19 Oct | Louny 09:58 | No data | — |
| Fri 16 Oct | Louny 09:58 | No data | — |
| Thu 15 Oct | Louny 09:58 | No data | — |
| Wed 14 Oct | Louny 09:58 | No data | — |
| Tue 13 Oct | Louny 09:58 | No data | — |
| Mon 12 Oct | Louny 09:58 | No data | — |
| Fri 9 Oct | Louny 09:58 | No data | — |
| Thu 8 Oct | Louny 09:58 | No data | — |
| Wed 7 Oct | Louny 09:58 | No data | — |
| Tue 6 Oct | Louny 09:58 | No data | — |
| Mon 5 Oct | — 10:11 | 0 min | — |
| Fri 2 Oct | — 10:12 | 0 min | — |
| Thu 1 Oct | — 10:11 | −1 min | — |
| Wed 30 Sept | — 10:18 | +7 min | +8 min |
| Tue 29 Sept | — 10:10 | −1 min | — |
| Fri 25 Sept | — 10:11 | 0 min | +1 min |
| Thu 24 Sept | — 10:12 | 0 min | +1 min |