Os 6526 6526 Žatec západ – Most
Alerts for train 6526
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 6526.
✓ Today’s run finished
Today, last fix heading to Most at 20:14 No data
- Žatec západ19:30
- Tvršice19:37
- Dolejší Hůrky19:40
- Postoloprty19:47
- Počerady19:54
- Volevčice19:57
- Most20:13
Next service: tomorrow 19:30 from Žatec západ · Sat 7 Nov
Last 30 days
Arrival delay at Most, 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 9 Aug Max en route +5 min · last fix heading to — +4 min
- Sun 27 Sept Max en route +3 min · last fix heading to — +3 min
- Wed 12 Aug Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
57 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 95% · 54
- 3–10 min 5% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 100% T n=8
- 88% W n=8
- 100% T n=8
- 100% F n=8
- 100% S n=8
- 78% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 57 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:30 | on time | on time | |
| 19:32 / 19:33 | ≈ on time | ≈ on time | |
| 19:37 | ≈ on time | ≈ +1 min | |
| 19:40 | ≈ on time | ≈ +1 min | |
| 19:42 | ≈ on time | ≈ +1 min | |
| 19:47 / 19:48 | ≈ on time | ≈ +1 min | |
| 19:52 | ≈ on time | ≈ +1 min | |
| 19:54 / 19:55 | ≈ on time | ≈ +1 min | |
| 19:57 | ≈ on time | ≈ +1 min | |
| 20:06 / 20:08 | ≈ on time | ≈ +1 min | |
| 20:13 | on time | +1 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 | Most 20:14 | No data | — |
| Thu 5 Nov | Most 20:14 | No data | — |
| Wed 4 Nov | Most 20:14 | No data | — |
| Tue 3 Nov | Most 20:14 | No data | — |
| Mon 2 Nov | Most 20:14 | No data | — |
| Sun 1 Nov | Most 20:14 | No data | — |
| Sat 31 Oct | Most 20:14 | No data | — |
| Fri 30 Oct | Most 20:14 | No data | — |
| Thu 29 Oct | Most 20:14 | No data | — |
| Wed 28 Oct | Most 20:14 | No data | — |
| Tue 27 Oct | Most 20:15 | No data | — |
| Mon 26 Oct | Most 20:14 | No data | — |
| Sun 25 Oct | Most 20:14 | No data | — |
| Sat 24 Oct | Most 20:14 | No data | — |
| Fri 23 Oct | Most 20:14 | No data | — |
| Thu 22 Oct | Most 20:14 | No data | — |
| Wed 21 Oct | Most 20:15 | No data | — |
| Tue 20 Oct | Most 20:14 | No data | — |
| Mon 19 Oct | Most 20:14 | No data | — |
| Sun 18 Oct | Most 20:14 | No data | — |
| Sat 17 Oct | Most 20:14 | No data | — |
| Fri 16 Oct | Most 20:14 | No data | — |
| Thu 15 Oct | Most 20:14 | No data | — |
| Wed 14 Oct | Most 20:14 | No data | — |
| Tue 13 Oct | Most 20:14 | No data | — |
| Mon 12 Oct | Most 20:15 | No data | — |
| Sun 11 Oct | Most 20:14 | No data | — |
| Sat 10 Oct | Most 20:14 | No data | — |
| Fri 9 Oct | Most 20:14 | No data | — |
| Thu 8 Oct | Most 20:14 | No data | — |