Os 17014 17014 Sokolov – Kraslice

View line Os 17014

Sokolov 13:44 → Kraslice 14:25 Mon, Tue, Wed, Thu, Fri 0 h 41 min · 9 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 13:44 from Sokolov · Thu 5 Nov

Next departure 13:44 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
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 21 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 29% · 7
  • On time 71% · 17
  • 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
13:44on time on time
13:46 / 13:47≈ on time ≈ on time
13:50≈ on time ≈ on time
13:55≈ on time ≈ on time
13:57 / 13:58≈ on time ≈ on time
14:06 / 14:08≈ 1 min early ≈ on time
14:15 / 14:16≈ 1 min early ≈ on time
14:21≈ 1 min early ≈ on time
14:251 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
Wed 4 NovKraslice 14:25No data—
Tue 3 NovKraslice 14:24No data—
Mon 2 NovKraslice 14:24No data—
Fri 30 OctKraslice 14:26No data—
Thu 29 OctKraslice 14:26No data—
Tue 27 OctKraslice 14:26No data—
Mon 26 OctKraslice 14:26No data—
Fri 23 OctKraslice 14:26No data—
Thu 22 OctKraslice 14:26No data—
Wed 21 OctKraslice 14:26No data—
Tue 20 OctKraslice 14:26No data—
Mon 19 OctKraslice 14:26No data—
Fri 16 OctKraslice 14:26No data—
Thu 15 OctKraslice 14:26No data—
Wed 14 OctKraslice 14:26No data—
Tue 13 OctKraslice 14:26No data—
Mon 12 OctKraslice 14:26No data—
Fri 9 OctKraslice 14:26No data—
Thu 8 OctKraslice 14:26No data—
Wed 7 OctKraslice 14:26No data—
Tue 6 OctKraslice 14:26No data—
Mon 5 Oct— 14:390 min—
Fri 2 Oct— 14:37−2 min+2 min
Thu 1 Oct— 14:37−2 min—
Wed 30 Sept— 14:400 min+1 min
Tue 29 Sept— 14:38−1 min—
Fri 25 Sept— 14:390 min—
Thu 24 Sept— 14:37−2 min—
Wed 23 Sept— 14:38−2 min—
Tue 22 Sept— 14:38−1 min—