Os 6509 6509 Most – Žatec západ

View line Os 6509

Most 09:42 → Žatec západ 10:25 Daily 0 h 43 min · 11 stops RegioJet ÚK a.s.

✓ Today’s run finished

Today, last fix heading to Žatec západ at 10:24 No data

  1. Most09:42
  2. Volevčice09:57
  3. Počerady09:59
  4. Postoloprty10:06
  5. Dolejší Hůrky10:14
  6. Tvršice10:17
  7. Žatec západ10:25

Next service: tomorrow 09:42 from Most · Sun 8 Nov

Next departure 09:42 tomorrow · Most
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
82%
47/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

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 30 Sept Max en route +12 min · last fix heading to — +11 min
  • Thu 20 Aug Max en route +8 min · last fix heading to — +8 min
  • Tue 18 Aug Max en route +5 min · last fix heading to — +5 min
  • Fri 25 Sept Max en route +6 min · last fix heading to — +4 min
  • Tue 22 Sept Max en route +4 min · last fix heading to — +4 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 82% · 47
  • 3–10 min 16% · 9
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 75% T n=8
  • 63% W n=8
  • 75% T n=8
  • 75% F n=8
  • 100% S n=8
  • 100% S n=8

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.

StopSched.Usually 9 days in 10
09:42on time on time
09:46 / 09:48≈ on time ≈ on time
09:57≈ on time ≈ +1 min
09:59 / 10:00≈ on time ≈ +2 min
10:02≈ on time ≈ +2 min
10:06 / 10:07≈ on time ≈ +2 min
10:12≈ on time ≈ +3 min
10:14≈ on time ≈ +3 min
10:17≈ on time ≈ +3 min
10:21 / 10:23≈ on time ≈ +4 min
10:25on time +4 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

DateLast stopFinalMax
Sat 7 NovŽatec západ 10:24No data—
Fri 6 NovŽatec západ 10:24No data—
Thu 5 NovŽatec západ 10:24No data—
Wed 4 NovŽatec západ 10:24No data—
Tue 3 NovŽatec západ 10:24No data—
Mon 2 NovŽatec západ 10:24No data—
Sun 1 NovŽatec západ 10:26No data—
Sat 31 OctŽatec západ 10:26No data—
Fri 30 OctŽatec západ 10:26No data—
Thu 29 OctŽatec západ 10:26No data—
Wed 28 OctŽatec západ 10:26No data—
Tue 27 OctŽatec západ 10:26No data—
Mon 26 OctŽatec západ 10:26No data—
Sun 25 OctŽatec západ 10:26No data—
Sat 24 OctŽatec západ 10:26No data—
Fri 23 OctŽatec západ 10:27No data—
Thu 22 OctŽatec západ 10:26No data—
Wed 21 OctŽatec západ 10:26No data—
Tue 20 OctŽatec západ 10:26No data—
Mon 19 OctŽatec západ 10:26No data—
Sun 18 OctŽatec západ 10:26No data—
Sat 17 OctŽatec západ 10:26No data—
Fri 16 OctŽatec západ 10:26No data—
Thu 15 OctŽatec západ 10:26No data—
Wed 14 OctŽatec západ 10:26No data—
Tue 13 OctŽatec západ 10:26No data—
Mon 12 OctŽatec západ 10:26No data—
Sun 11 OctŽatec západ 10:26No data—
Sat 10 OctŽatec západ 10:26No data—
Fri 9 OctŽatec západ 10:26No data—