Os 6500 6500 Žatec západ – Most

View line Os 6500

Žatec západ 04:31 → Most 05:13 Mon, Tue, Wed, Thu, Fri 0 h 42 min · 11 stops RegioJet ÚK a.s.

✓ Today’s run finished

Today, last fix heading to Most at 05:14 No data

  1. Žatec západ04:31
  2. Tvršice04:38
  3. Dolejší Hůrky04:41
  4. Postoloprty04:48
  5. Počerady04:55
  6. Volevčice04:58
  7. Most05:13

Next service: tomorrow 04:31 from Žatec západ · Wed 11 Nov

Next departure 04:31 tomorrow · Žatec západ
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
95%
35/37 runs under 3 min
RT coverage: 37 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

  • Tue 22 Sept Max en route +10 min · last fix heading to — +6 min
  • Mon 14 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 35
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 86% T n=7
  • 100% W n=7
  • 100% T n=8
  • 100% 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, 37 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
04:31on time +1 min
04:33 / 04:34≈ on time ≈ +1 min
04:38≈ on time ≈ +1 min
04:41≈ on time ≈ +1 min
04:43≈ on time ≈ +1 min
04:48 / 04:49≈ on time ≈ +1 min
04:53≈ on time ≈ +1 min
04:55 / 04:56≈ on time ≈ on time
04:58≈ on time ≈ on time
05:07 / 05:08≈ on time ≈ on time
05:13on time on time

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
Tue 10 NovMost 05:14No data—
Mon 9 NovMost 05:14No data—
Fri 6 NovMost 05:14No data—
Thu 5 NovMost 05:14No data—
Wed 4 NovMost 05:14No data—
Tue 3 NovMost 05:15No data—
Mon 2 NovMost 05:14No data—
Fri 30 OctMost 05:14No data—
Thu 29 OctMost 05:14No data—
Tue 27 OctMost 05:14No data—
Mon 26 OctMost 05:14No data—
Fri 23 OctMost 05:14No data—
Thu 22 OctMost 05:14No data—
Wed 21 OctMost 05:14No data—
Tue 20 OctMost 05:14No data—
Mon 19 OctMost 05:14No data—
Fri 16 OctMost 05:14No data—
Thu 15 OctMost 05:14No data—
Wed 14 OctMost 05:14No data—
Tue 13 OctMost 05:14No data—
Mon 12 OctMost 05:14No data—
Fri 9 OctMost 05:14No data—
Thu 8 OctMost 05:14No data—
Wed 7 OctMost 05:14No data—
Tue 6 OctMost 05:14No data—
Mon 5 Oct— 05:280 min—
Fri 2 Oct— 05:270 min+1 min
Thu 1 Oct— 05:270 min—
Wed 30 Sept— 05:270 min—
Tue 29 Sept— 05:270 min—