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

View line Os 7008

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

✓ Today’s run finished

Today, last fix heading to Cheb at 14:24 No data

  1. Klášterec nad Ohří12:41
  2. Stráž nad Ohří12:55
  3. Hájek13:15
  4. Chodov13:39
  5. Sokolov13:51
  6. Kynšperk n.O.14:08
  7. Cheb14:23

Next service: Monday 12:41 from Klášterec nad Ohří · Mon 9 Nov

Next departure 12:41 Monday · Klášterec nad Ohří
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
88%
35/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 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 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 +21 min · last fix heading to — +13 min
  • Wed 19 Aug Max en route +13 min · last fix heading to — +12 min
  • Wed 2 Sept Max en route +9 min · last fix heading to — +7 min
  • Fri 21 Aug Max en route +9 min · last fix heading to — +7 min
  • Fri 11 Sept Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 85% · 34
  • 3–10 min 8% · 3
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 75% W n=8
  • 88% 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 (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
12:41on time on time
12:45≈ on time ≈ on time
12:48 / 12:49≈ on time ≈ +1 min
12:52≈ on time ≈ +1 min
12:55 / 12:56≈ on time ≈ +1 min
13:01 / 13:02≈ on time ≈ +1 min
13:08 / 13:09≈ on time ≈ +1 min
13:15≈ on time ≈ +1 min
13:22≈ on time ≈ +2 min
13:25 / 13:27≈ on time ≈ +2 min
13:33 / 13:34≈ on time ≈ +2 min
13:39 / 13:40≈ on time ≈ +2 min
13:43≈ on time ≈ +3 min
13:48≈ on time ≈ +3 min
13:51 / 13:52≈ on time ≈ +3 min
13:56≈ on time ≈ +3 min
13:58≈ on time ≈ +3 min
14:02 / 14:03≈ on time ≈ +3 min
14:08 / 14:09≈ on time ≈ +4 min
14:12≈ on time ≈ +4 min
14:17≈ on time ≈ +4 min
14:23on 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
Fri 6 NovCheb 14:24No data—
Thu 5 NovCheb 14:24No data—
Wed 4 NovCheb 14:25No data—
Tue 3 NovCheb 14:24No data—
Mon 2 NovCheb 14:24No data—
Fri 30 OctCheb 14:24No data—
Thu 29 OctCheb 14:24No data—
Tue 27 OctCheb 14:24No data—
Mon 26 OctCheb 14:24No data—
Fri 23 OctCheb 14:24No data—
Thu 22 OctCheb 14:24No data—
Wed 21 OctCheb 14:24No data—
Tue 20 OctCheb 14:24No data—
Mon 19 OctCheb 14:24No data—
Fri 16 OctCheb 14:24No data—
Thu 15 OctCheb 14:24No data—
Wed 14 OctCheb 14:24No data—
Tue 13 OctCheb 14:24No data—
Mon 12 OctCheb 14:24No data—
Fri 9 OctCheb 14:24No data—
Thu 8 OctCheb 14:24No data—
Wed 7 OctCheb 14:24No data—
Tue 6 OctCheb 14:24No data—
Mon 5 Oct— 14:370 min—
Fri 2 Oct— 14:370 min+4 min
Thu 1 Oct— 14:36−1 min+1 min
Wed 30 Sept— 14:37−1 min—
Tue 29 Sept— 14:36−1 min+2 min
Fri 25 Sept— 14:370 min+1 min
Thu 24 Sept— 14:380 min+2 min