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