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