Os 17007 17007 Kraslice – Sokolov

View line Os 17007

Kraslice 06:06 → Sokolov 06:44 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: Wednesday 4 November No data

Next service: today 06:06 from Kraslice · Thu 5 Nov

Next departure 06:06 today · Kraslice
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
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 21 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 Sokolov, in minutes. One bar per run.

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

Worst days

  • Fri 11 Sept Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 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
  • 80% 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:06on time on time
06:09≈ on time ≈ on time
06:14 / 06:16≈ on time ≈ on time
06:23 / 06:24≈ on time ≈ on time
06:31≈ on time ≈ on time
06:33≈ on time ≈ on time
06:38≈ on time ≈ on time
06:40 / 06:41≈ on time ≈ on time
06:44on 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
Wed 4 NovSokolov 06:44No data—
Tue 3 NovSokolov 06:44No data—
Mon 2 NovSokolov 06:44No data—
Fri 30 OctSokolov 06:45No data—
Thu 29 OctSokolov 06:45No data—
Tue 27 OctSokolov 06:45No data—
Mon 26 OctSokolov 06:45No data—
Fri 23 OctSokolov 06:45No data—
Thu 22 OctSokolov 06:45No data—
Wed 21 OctSokolov 06:45No data—
Tue 20 OctSokolov 06:45No data—
Mon 19 OctSokolov 06:45No data—
Fri 16 OctSokolov 06:45No data—
Thu 15 OctSokolov 06:45No data—
Wed 14 OctSokolov 06:45No data—
Tue 13 OctSokolov 06:45No data—
Mon 12 OctSokolov 06:45No data—
Fri 9 OctSokolov 06:45No data—
Thu 8 OctSokolov 06:45No data—
Wed 7 OctSokolov 06:45No data—
Tue 6 OctSokolov 06:45No data—
Mon 5 Oct— 06:590 min—
Fri 2 Oct— 06:58−1 min—
Thu 1 Oct— 06:590 min—
Wed 30 Sept— 06:580 min+1 min
Tue 29 Sept— 06:580 min—
Fri 25 Sept— 06:590 min—
Thu 24 Sept— 06:580 min—
Wed 23 Sept— 06:580 min—
Tue 22 Sept— 06:580 min—