Os 17023 17023 Kraslice – Sokolov

View line Os 17023

Kraslice 15:50 → Sokolov 16:28 Sat, Sun 0 h 38 min · 9 stops GW Train Regio a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: tomorrow 15:50 from Kraslice · Sat 7 Nov

Next departure 15:50 tomorrow · 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
91%
31/34 runs under 3 min
RT coverage: 34 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

  • Sat 3 Oct Max en route +29 min · last fix heading to — +23 min
  • Mon 31 Aug Max en route +5 min · last fix heading to — +4 min
  • Wed 26 Aug Max en route +13 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 6% · 2
  • On time 85% · 29
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 67% W n=3
  • 100% T n=3
  • 100% F n=3
  • 88% S n=8
  • 100% S n=9

Stops and timetable

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

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