Os 7004 7004 Klášterec nad Ohří – Cheb

View line Os 7004

Klášterec nad Ohří 14:41 → Cheb 16:25 Mon, Tue, Wed, Thu, Fri 1 h 44 min · 22 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 14:41 from Klášterec nad Ohří · Thu 5 Nov

Next departure 14:41 today · Klášterec nad Ohří
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
75%
30/40 runs under 3 min
RT coverage: 40 full · 0 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Cheb, 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 +14 min · last fix heading to — +11 min
  • Mon 5 Oct Max en route +7 min · last fix heading to — +7 min
  • Thu 27 Aug Max en route +7 min · last fix heading to — +6 min
  • Thu 13 Aug Max en route +7 min · last fix heading to — +6 min
  • Thu 17 Sept Max en route +5 min · last fix heading to — +5 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 75% · 30
  • 3–10 min 23% · 9
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 88% T n=8
  • 75% W n=8
  • 38% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (22 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
14:41on time +1 min
14:45≈ on time ≈ +1 min
14:48 / 14:49≈ on time ≈ +1 min
14:52≈ on time ≈ +1 min
14:55 / 14:56≈ on time ≈ +1 min
15:01 / 15:02≈ on time ≈ +2 min
15:08 / 15:09≈ on time ≈ +2 min
15:15≈ on time ≈ +2 min
15:22≈ on time ≈ +2 min
15:25 / 15:29≈ on time ≈ +2 min
15:35 / 15:36≈ on time ≈ +3 min
15:41 / 15:42≈ on time ≈ +3 min
15:45≈ on time ≈ +3 min
15:50≈ on time ≈ +3 min
15:53 / 15:54≈ on time ≈ +4 min
15:58≈ on time ≈ +4 min
16:00≈ on time ≈ +4 min
16:04 / 16:05≈ on time ≈ +4 min
16:10 / 16:11≈ on time ≈ +4 min
16:14≈ on time ≈ +5 min
16:19≈ on time ≈ +5 min
16:25on time +5 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
Wed 4 NovCheb 16:24No data—
Tue 3 NovCheb 16:24No data—
Mon 2 NovCheb 16:24No data—
Fri 30 OctCheb 16:26No data—
Thu 29 OctCheb 16:26No data—
Tue 27 OctCheb 16:26No data—
Mon 26 OctCheb 16:26No data—
Fri 23 OctCheb 16:26No data—
Thu 22 OctCheb 16:26No data—
Wed 21 OctCheb 16:26No data—
Tue 20 OctCheb 16:26No data—
Mon 19 OctCheb 16:26No data—
Fri 16 OctCheb 16:26No data—
Thu 15 OctCheb 16:26No data—
Wed 14 OctCheb 16:26No data—
Tue 13 OctCheb 16:26No data—
Mon 12 OctCheb 16:26No data—
Fri 9 OctCheb 16:26No data—
Thu 8 OctCheb 16:26No data—
Wed 7 OctCheb 16:26No data—
Tue 6 OctCheb 16:26No data—
Mon 5 Oct— 16:47+7 min+7 min
Fri 2 Oct— 16:42+3 min+3 min
Thu 1 Oct— 16:390 min+1 min
Wed 30 Sept— 16:400 min+5 min
Tue 29 Sept— 16:390 min—
Fri 25 Sept— 16:400 min+2 min
Thu 24 Sept— 16:41+2 min+4 min
Wed 23 Sept— 16:410 min+2 min
Tue 22 Sept— 16:390 min+1 min