Os 6521 6521 Most – Žatec západ
Alerts for train 6521
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 6521.
✓ Today’s run finished
Today, last fix heading to Žatec západ at 17:24 No data
- Most16:42
- Volevčice16:57
- Počerady16:59
- Postoloprty17:06
- Dolejší Hůrky17:14
- Tvršice17:17
- Žatec západ17:25
Next service: tomorrow 16:42 from Most · Thu 12 Nov
Last 30 days
Arrival delay at Žatec západ, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 16 Sept Max en route +10 min · last fix heading to — +8 min
- Thu 20 Aug Max en route +9 min · last fix heading to — +6 min
- Fri 14 Aug Max en route +3 min · last fix heading to — +3 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 33
- 3–10 min 8% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=7
- 100% T n=7
- 86% W n=7
- 86% T n=7
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 16:42 | on time | on time | |
| 16:46 / 16:48 | ≈ on time | ≈ on time | |
| 16:57 | ≈ on time | ≈ +1 min | |
| 16:59 / 17:00 | ≈ on time | ≈ +1 min | |
| 17:02 | ≈ on time | ≈ +1 min | |
| 17:06 / 17:07 | ≈ on time | ≈ +1 min | |
| 17:12 | ≈ on time | ≈ +1 min | |
| 17:14 | ≈ on time | ≈ +1 min | |
| 17:17 | ≈ on time | ≈ +2 min | |
| 17:21 / 17:23 | ≈ on time | ≈ +2 min | |
| 17:25 | 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 |
|---|---|---|---|
| Wed 11 Nov | Žatec západ 17:24 | No data | — |
| Tue 10 Nov | Žatec západ 17:24 | No data | — |
| Mon 9 Nov | Žatec západ 17:24 | No data | — |
| Fri 6 Nov | Žatec západ 17:24 | No data | — |
| Thu 5 Nov | Žatec západ 17:24 | No data | — |
| Wed 4 Nov | Žatec západ 17:24 | No data | — |
| Tue 3 Nov | Žatec západ 17:24 | No data | — |
| Mon 2 Nov | Žatec západ 17:24 | No data | — |
| Fri 30 Oct | Žatec západ 17:26 | No data | — |
| Thu 29 Oct | Žatec západ 17:26 | No data | — |
| Tue 27 Oct | Žatec západ 17:26 | No data | — |
| Mon 26 Oct | Žatec západ 17:26 | No data | — |
| Fri 23 Oct | Žatec západ 17:27 | No data | — |
| Thu 22 Oct | Žatec západ 17:26 | No data | — |
| Wed 21 Oct | Žatec západ 17:26 | No data | — |
| Tue 20 Oct | Žatec západ 17:27 | No data | — |
| Mon 19 Oct | Žatec západ 17:26 | No data | — |
| Fri 16 Oct | Žatec západ 17:26 | No data | — |
| Thu 15 Oct | Žatec západ 17:26 | No data | — |
| Wed 14 Oct | Žatec západ 17:26 | No data | — |
| Tue 13 Oct | Žatec západ 17:26 | No data | — |
| Mon 12 Oct | Žatec západ 17:27 | No data | — |
| Fri 9 Oct | Žatec západ 17:26 | No data | — |
| Thu 8 Oct | Žatec západ 17:26 | No data | — |
| Wed 7 Oct | Žatec západ 17:26 | No data | — |
| Tue 6 Oct | Žatec západ 17:26 | No data | — |
| Mon 5 Oct | Žatec západ 17:26 | 0 min | — |
| Fri 2 Oct | — 17:39 | 0 min | — |
| Thu 1 Oct | — 17:39 | 0 min | — |
| Wed 30 Sept | — 17:40 | 0 min | +2 min |