Os 17008 17008 Sokolov – Kraslice

View line Os 17008

Sokolov 06:50 → Kraslice 07:28 Mon, Tue, Wed, Thu, Fri 0 h 38 min · 9 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 06:50 from Sokolov · Mon 9 Nov

Next departure 06:50 today · Sokolov
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 23 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Kraslice, 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

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

  • Early 25% · 6
  • On time 75% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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:50on time on time
06:52 / 06:53≈ on time ≈ on time
06:55≈ on time ≈ on time
07:00≈ on time ≈ on time
07:02≈ on time ≈ on time
07:10 / 07:12≈ 1 min early ≈ on time
07:18 / 07:19≈ 1 min early ≈ on time
07:24≈ 1 min early ≈ on time
07:281 min early 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
Fri 6 NovKraslice 07:29No data—
Thu 5 NovKraslice 07:29No data—
Wed 4 NovKraslice 07:29No data—
Tue 3 NovKraslice 07:29No data—
Mon 2 NovKraslice 07:29No data—
Fri 30 OctKraslice 07:29No data—
Thu 29 OctKraslice 07:29No data—
Tue 27 OctKraslice 07:29No data—
Mon 26 OctKraslice 07:29No data—
Fri 23 OctKraslice 07:29No data—
Thu 22 OctKraslice 07:29No data—
Wed 21 OctKraslice 07:29No data—
Tue 20 OctKraslice 07:29No data—
Mon 19 OctKraslice 07:29No data—
Fri 16 OctKraslice 07:29No data—
Thu 15 OctKraslice 07:29No data—
Wed 14 OctKraslice 07:29No data—
Tue 13 OctKraslice 07:29No data—
Mon 12 OctKraslice 07:29No data—
Fri 9 OctKraslice 07:29No data—
Thu 8 OctKraslice 07:30No data—
Wed 7 OctKraslice 07:29No data—
Tue 6 OctKraslice 07:29No data—
Mon 5 Oct— 07:430 min—
Fri 2 Oct— 07:41−2 min—
Thu 1 Oct— 07:41−1 min—
Wed 30 Sept— 07:420 min—
Tue 29 Sept— 07:41−1 min—
Fri 25 Sept— 07:41−1 min—
Thu 24 Sept— 07:40−2 min+1 min