Os 17015 17015 Kraslice – Sokolov

View line Os 17015

Kraslice 08:50 → Sokolov 09:27 Mon, Tue, Wed, Thu, Fri 0 h 37 min · 9 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 08:50 from Kraslice · Fri 6 Nov

Next departure 08:50 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
95%
38/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 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

  • Tue 25 Aug Max en route +8 min · last fix heading to — +8 min
  • Tue 22 Sept Max en route +9 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 75% 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, 40 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
08:50on time +1 min
08:53≈ on time ≈ +1 min
08:58 / 09:00≈ on time ≈ +1 min
09:06 / 09:07≈ on time ≈ +1 min
09:14≈ on time ≈ +1 min
09:16≈ on time ≈ +1 min
09:21≈ on time ≈ on time
09:23 / 09:24≈ on time ≈ on time
09:27on 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 NovSokolov 09:28No data—
Wed 4 NovSokolov 09:28No data—
Tue 3 NovSokolov 09:28No data—
Mon 2 NovSokolov 09:28No data—
Fri 30 OctSokolov 09:28No data—
Thu 29 OctSokolov 09:28No data—
Tue 27 OctSokolov 09:28No data—
Mon 26 OctSokolov 09:28No data—
Fri 23 OctSokolov 09:29No data—
Thu 22 OctSokolov 09:29No data—
Wed 21 OctSokolov 09:28No data—
Tue 20 OctSokolov 09:28No data—
Mon 19 OctSokolov 09:28No data—
Fri 16 OctSokolov 09:29No data—
Thu 15 OctSokolov 09:28No data—
Wed 14 OctSokolov 09:28No data—
Tue 13 OctSokolov 09:28No data—
Mon 12 OctSokolov 09:28No data—
Fri 9 OctSokolov 09:28No data—
Thu 8 OctSokolov 09:28No data—
Wed 7 OctSokolov 09:28No data—
Tue 6 OctSokolov 09:28No data—
Mon 5 Oct— 09:40−1 min—
Fri 2 Oct— 09:41−1 min—
Thu 1 Oct— 09:420 min+1 min
Wed 30 Sept— 09:410 min—
Tue 29 Sept— 09:41−1 min—
Fri 25 Sept— 09:40−1 min—
Thu 24 Sept— 09:420 min—
Wed 23 Sept— 09:41−1 min—