Os 17026 17026 Sokolov – Kraslice

View line Os 17026

Sokolov 17:32 → Kraslice 18:08 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 9 stops GW Train Regio a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 17:32 from Sokolov · Mon 9 Nov

Next departure 17:32 tomorrow · 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
95%
36/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+1min
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

Worst days

  • Mon 31 Aug Max en route +5 min · last fix heading to — +5 min
  • Tue 18 Aug Max en route +8 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 21% · 8
  • On time 74% · 28
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 88% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 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
17:32on time on time
17:34 / 17:35≈ on time ≈ on time
17:37≈ on time ≈ on time
17:41≈ on time ≈ +1 min
17:43 / 17:44≈ on time ≈ +1 min
17:51 / 17:52≈ 1 min early ≈ +1 min
17:58 / 17:59≈ 1 min early ≈ +1 min
18:04≈ 1 min early ≈ +1 min
18:081 min early +1 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 NovKraslice 18:09No data—
Thu 5 NovKraslice 18:09No data—
Wed 4 NovKraslice 18:09No data—
Tue 3 NovKraslice 18:09No data—
Mon 2 NovKraslice 18:09No data—
Fri 30 OctKraslice 18:09No data—
Thu 29 OctKraslice 18:09No data—
Tue 27 OctKraslice 18:10No data—
Mon 26 OctKraslice 18:09No data—
Fri 23 OctKraslice 18:09No data—
Thu 22 OctKraslice 18:09No data—
Wed 21 OctKraslice 18:09No data—
Tue 20 OctKraslice 18:10No data—
Mon 19 OctKraslice 18:09No data—
Fri 16 OctKraslice 18:09No data—
Thu 15 OctKraslice 18:09No data—
Wed 14 OctKraslice 18:09No data—
Tue 13 OctKraslice 18:09No data—
Mon 12 OctKraslice 18:10No data—
Fri 9 OctKraslice 18:09No data—
Thu 8 OctKraslice 18:09No data—
Wed 7 OctKraslice 18:09No data—
Tue 6 OctKraslice 18:09No data—
Mon 5 OctKraslice 18:09No data—
Fri 2 Oct— 18:21−1 min—
Thu 1 Oct— 18:22−1 min—
Wed 30 Sept— 18:230 min—
Tue 29 Sept— 18:21−1 min—
Fri 25 Sept— 18:230 min—
Thu 24 Sept— 18:21−1 min—