Os 6505 6505 Most – Žatec západ

View line Os 6505

Most 06:42 → Žatec západ 07:25 Mon, Tue, Wed, Thu, Fri 0 h 43 min · 11 stops RegioJet ÚK a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 06:42 from Most · Mon 9 Nov

Next departure 06:42 Monday · Most
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
80%
32/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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

  • Thu 20 Aug Max en route +19 min · last fix heading to — +17 min
  • Fri 28 Aug Max en route +13 min · last fix heading to — +8 min
  • Wed 26 Aug Max en route +4 min · last fix heading to — +4 min
  • Tue 29 Sept Max en route +4 min · last fix heading to — +3 min
  • Tue 15 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

40 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 80% · 32
  • 3–10 min 18% · 7
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 75% T n=8
  • 75% W n=8
  • 75% T n=8
  • 75% 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, 40 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
06:42on time on time
06:46 / 06:48≈ on time ≈ on time
06:57≈ on time ≈ +1 min
06:59 / 07:00≈ on time ≈ +1 min
07:02≈ on time ≈ +1 min
07:06 / 07:07≈ on time ≈ +2 min
07:12≈ on time ≈ +2 min
07:14≈ on time ≈ +2 min
07:17≈ on time ≈ +2 min
07:21 / 07:23≈ on time ≈ +3 min
07:25on time +3 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
Fri 6 NovŽatec západ 07:24No data—
Thu 5 NovŽatec západ 07:24No data—
Wed 4 NovŽatec západ 07:24No data—
Tue 3 NovŽatec západ 07:24No data—
Mon 2 NovŽatec západ 07:24No data—
Fri 30 OctŽatec západ 07:26No data—
Thu 29 OctŽatec západ 07:26No data—
Tue 27 OctŽatec západ 07:26No data—
Mon 26 OctŽatec západ 07:26No data—
Fri 23 OctŽatec západ 07:26No data—
Thu 22 OctŽatec západ 07:26No data—
Wed 21 OctŽatec západ 07:26No data—
Tue 20 OctŽatec západ 07:26No data—
Mon 19 OctŽatec západ 07:26No data—
Fri 16 OctŽatec západ 07:26No data—
Thu 15 OctŽatec západ 07:26No data—
Wed 14 OctŽatec západ 07:26No data—
Tue 13 OctŽatec západ 07:26No data—
Mon 12 OctŽatec západ 07:26No data—
Fri 9 OctŽatec západ 07:26No data—
Thu 8 OctŽatec západ 07:27No data—
Wed 7 OctŽatec západ 07:26No data—
Tue 6 OctŽatec západ 07:26No data—
Mon 5 Oct— 07:42+2 min+3 min
Fri 2 Oct— 07:400 min+1 min
Thu 1 Oct— 07:410 min+2 min
Wed 30 Sept— 07:41+2 min+3 min
Tue 29 Sept— 07:42+3 min+4 min
Fri 25 Sept— 07:41+2 min+3 min
Thu 24 Sept— 07:390 min+2 min