Os 20804 20804 Kraslice – Klingenthal

View line Os 20804

Kraslice 06:09 → Klingenthal 06:14 Daily 0 h 05 min · 3 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Klingenthal at 06:14 No data

  1. Kraslice06:09
  2. Kraslice-P.vlekem z06:10
  3. Klingenthal06:14

Next service: tomorrow 06:09 from Kraslice · Fri 6 Nov

Next departure 06:09 tomorrow · Kraslice
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
100%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 31 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 Klingenthal, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 58
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=7
  • 100% T n=8
  • 100% F n=8
  • 100% S n=9
  • 100% S n=9

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 stops).

Last 90 days, 58 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:09on time on time
06:10≈ on time ≈ on time
06:14on 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
Thu 5 NovKlingenthal 06:14No data—
Wed 4 NovKlingenthal 06:14No data—
Tue 3 NovKlingenthal 06:14No data—
Mon 2 NovKlingenthal 06:14No data—
Sun 1 NovKlingenthal 06:15No data—
Sat 31 OctKlingenthal 06:15No data—
Fri 30 OctKlingenthal 06:15No data—
Thu 29 OctKlingenthal 06:15No data—
Wed 28 OctKlingenthal 06:15No data—
Tue 27 OctKlingenthal 06:15No data—
Mon 26 OctKlingenthal 06:15No data—
Sun 25 OctKlingenthal 06:15No data—
Sat 24 OctKlingenthal 06:15No data—
Fri 23 OctKlingenthal 06:15No data—
Thu 22 OctKlingenthal 06:15No data—
Wed 21 OctKlingenthal 06:15No data—
Tue 20 OctKlingenthal 06:15No data—
Mon 19 OctKlingenthal 06:15No data—
Sun 18 OctKlingenthal 06:15No data—
Sat 17 OctKlingenthal 06:15No data—
Fri 16 OctKlingenthal 06:15No data—
Thu 15 OctKlingenthal 06:15No data—
Wed 14 OctKlingenthal 06:15No data—
Tue 13 OctKlingenthal 06:15No data—
Mon 12 OctKlingenthal 06:15No data—
Sun 11 OctKlingenthal 06:15No data—
Sat 10 OctKlingenthal 06:15No data—
Fri 9 OctKlingenthal 06:15No data—
Thu 8 OctKlingenthal 06:15No data—
Wed 7 OctKlingenthal 06:15No data—