Os 17019 17019 Kraslice – Sokolov

View line Os 17019

Kraslice 14:50 → Sokolov 15:32 Mon, Tue, Wed, Thu, Fri 0 h 42 min · 9 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Sokolov at 15:33 No data

  1. Kraslice14:50
  2. Kraslice př. nz14:53
  3. Oloví15:06
  4. Hřebeny15:19
  5. Luh nad Svatavou z15:21
  6. Svatava15:28
  7. Sokolov15:32

Next service: Monday 14:50 from Kraslice · Mon 9 Nov

Next departure 14:50 Monday · Kraslice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 23 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

  • Wed 16 Sept Max en route +4 min · last fix heading to — +4 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
  • 80% 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
14:50on time +1 min
14:53≈ on time ≈ +1 min
14:58 / 15:00≈ on time ≈ +1 min
15:06 / 15:12≈ on time ≈ +1 min
15:19≈ on time ≈ +2 min
15:21≈ on time ≈ +2 min
15:26≈ on time ≈ +2 min
15:28 / 15:29≈ on time ≈ +2 min
15:32on 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
Fri 6 NovSokolov 15:33No data—
Thu 5 NovSokolov 15:33No data—
Wed 4 NovSokolov 15:34No data—
Tue 3 NovSokolov 15:33No data—
Mon 2 NovSokolov 15:33No data—
Fri 30 OctSokolov 15:33No data—
Thu 29 OctSokolov 15:33No data—
Tue 27 OctSokolov 15:33No data—
Mon 26 OctSokolov 15:33No data—
Fri 23 OctSokolov 15:33No data—
Thu 22 OctSokolov 15:33No data—
Wed 21 OctSokolov 15:33No data—
Tue 20 OctSokolov 15:33No data—
Mon 19 OctSokolov 15:33No data—
Fri 16 OctSokolov 15:33No data—
Thu 15 OctSokolov 15:33No data—
Wed 14 OctSokolov 15:33No data—
Tue 13 OctSokolov 15:33No data—
Mon 12 OctSokolov 15:33No data—
Fri 9 OctSokolov 15:33No data—
Thu 8 OctSokolov 15:33No data—
Wed 7 OctSokolov 15:33No data—
Tue 6 OctSokolov 15:33No data—
Mon 5 Oct— 15:470 min—
Fri 2 Oct— 15:480 min+1 min
Thu 1 Oct— 15:460 min+1 min
Wed 30 Sept— 15:480 min—
Tue 29 Sept— 15:460 min+1 min
Fri 25 Sept— 15:46−1 min—
Thu 24 Sept— 15:470 min—