Os 17009 17009 Kraslice – Sokolov

View line Os 17009

Kraslice 06:50 → Sokolov 07:27 Sat, Sun 0 h 37 min · 9 stops GW Train Regio a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: Saturday 06:50 from Kraslice · Sat 7 Nov

Next departure 06:50 Saturday · Kraslice
On-time · 30 days
—
Too little data (0/9 runs with data)
RT coverage: 0 full · 0 partial · 9 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 35 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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 +6 min · last fix heading to — +6 min
  • Sat 29 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 33
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 100% W n=3
  • 100% T n=3
  • 100% F n=3
  • 89% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 35 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 +1 min
06:53≈ on time ≈ +1 min
06:58 / 07:00≈ on time ≈ +2 min
07:06 / 07:07≈ on time ≈ +3 min
07:14≈ on time ≈ +2 min
07:16≈ on time ≈ +2 min
07:21≈ on time ≈ +2 min
07:23 / 07:24≈ on time ≈ +2 min
07:27on time +2 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
Sun 1 NovSokolov 07:28No data—
Sat 31 OctSokolov 07:28No data—
Wed 28 OctSokolov 07:28No data—
Sun 25 OctSokolov 07:28No data—
Sat 24 OctSokolov 07:28No data—
Sun 18 OctSokolov 07:29No data—
Sat 17 OctSokolov 07:28No data—
Sun 11 OctSokolov 07:28No data—
Sat 10 OctSokolov 07:28No data—
Sun 4 Oct— 07:41−1 min—
Sat 3 Oct— 07:410 min—
Mon 28 Sept— 07:420 min—
Sun 27 Sept— 07:41−1 min—
Sat 26 Sept— 07:420 min—
Sun 20 Sept— 07:40−1 min—
Sat 19 Sept— 07:420 min—
Sun 13 Sept— 07:410 min—
Sat 12 Sept— 07:41−1 min—
Sun 6 Sept— 07:410 min—
Sat 5 Sept— 07:40−1 min—
Mon 31 Aug— 07:410 min—
Sun 30 Aug— 07:420 min—
Sat 29 Aug— 07:44+3 min+3 min
Fri 28 Aug— 07:420 min—
Thu 27 Aug— 07:43+1 min+5 min
Wed 26 Aug— 07:43+2 min+2 min
Tue 25 Aug— 08:12+6 min+6 min
Mon 24 Aug— 07:420 min—
Sun 23 Aug— 07:410 min—
Sat 22 Aug— 07:410 min—