Os 20828 20828 Sokolov – Klingenthal

View line Os 20828

Sokolov 18:32 → Klingenthal 19:14 Mon, Tue, Wed, Thu, Fri 0 h 42 min · 11 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 18:32 from Sokolov · Mon 9 Nov

Next departure 18:32 today · Sokolov
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
92%
35/38 runs under 3 min
RT coverage: 38 full · 0 partial · 25 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Klingenthal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 31 Aug Max en route +4 min · last fix heading to — +4 min
  • Fri 21 Aug Max en route +8 min · last fix heading to — +4 min
  • Fri 28 Aug Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 35
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=8
  • 100% 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, 38 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
18:32+3 min +5 min
18:34 / 18:35≈ +3 min ≈ +5 min
18:37≈ +3 min ≈ +5 min
18:41≈ +3 min ≈ +4 min
18:43 / 18:44≈ +2 min ≈ +4 min
18:51 / 18:52≈ +2 min ≈ +3 min
18:58 / 18:59≈ +2 min ≈ +3 min
19:04≈ +1 min ≈ +2 min
19:08 / 19:09≈ +1 min ≈ +2 min
19:10≈ +1 min ≈ +2 min
19:14+1 min +2 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 NovKlingenthal 19:14No data—
Thu 5 NovKlingenthal 19:14No data—
Wed 4 NovKlingenthal 19:14No data—
Tue 3 NovKlingenthal 19:14No data—
Mon 2 NovKlingenthal 19:14No data—
Fri 30 OctKlingenthal 19:15No data—
Thu 29 OctKlingenthal 19:15No data—
Wed 28 OctKlingenthal 19:15No data—
Tue 27 OctKlingenthal 19:16No data—
Mon 26 OctKlingenthal 19:15No data—
Fri 23 OctKlingenthal 19:16No data—
Thu 22 OctKlingenthal 19:15No data—
Wed 21 OctKlingenthal 19:15No data—
Tue 20 OctKlingenthal 19:15No data—
Mon 19 OctKlingenthal 19:16No data—
Fri 16 OctKlingenthal 19:15No data—
Thu 15 OctKlingenthal 19:15No data—
Wed 14 OctKlingenthal 19:16No data—
Tue 13 OctKlingenthal 19:15No data—
Mon 12 OctKlingenthal 19:16No data—
Fri 9 OctKlingenthal 19:15No data—
Thu 8 OctKlingenthal 19:16No data—
Wed 7 OctKlingenthal 19:15No data—
Tue 6 OctKlingenthal 19:15No data—
Mon 5 OctKlingenthal 19:15No data—
Fri 2 Oct— 19:28+1 min+5 min
Thu 1 Oct— 19:270 min+3 min
Wed 30 Sept— 19:270 min+3 min
Tue 29 Sept— 19:29+2 min+3 min
Mon 28 Sept— 19:280 min—