Os 17027 17027 Kraslice – Sokolov

View line Os 17027

Kraslice 19:44 → Sokolov 20:20 Daily 0 h 36 min · 9 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Sokolov at 20:19 No data

  1. Kraslice19:44
  2. Kraslice př. nz19:47
  3. Oloví19:59
  4. Hřebeny20:07
  5. Luh nad Svatavou z20:09
  6. Svatava20:16
  7. Sokolov20:20

Next service: tomorrow 19:44 from Kraslice · Mon 9 Nov

Next departure 19:44 tomorrow · Kraslice
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
87%
48/55 runs under 3 min
RT coverage: 55 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
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 +15 min · last fix heading to — +15 min
  • Sat 29 Aug Max en route +14 min · last fix heading to — +14 min
  • Wed 26 Aug Max en route +12 min · last fix heading to — +12 min
  • Sun 30 Aug Max en route +11 min · last fix heading to — +11 min
  • Mon 31 Aug Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 48
  • 3–10 min 5% · 3
  • 10–30 min 7% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 88% T n=8
  • 88% W n=8
  • 100% T n=8
  • 88% F n=8
  • 75% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 55 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
19:44on time on time
19:47≈ on time ≈ +1 min
19:52 / 19:53≈ on time ≈ +1 min
19:59 / 20:00≈ on time ≈ +2 min
20:07≈ on time ≈ +3 min
20:09≈ on time ≈ +3 min
20:14≈ on time ≈ +4 min
20:16 / 20:17≈ on time ≈ +4 min
20:20on time +4 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 8 NovSokolov 20:19No data—
Sat 7 NovSokolov 20:19No data—
Fri 6 NovSokolov 20:19No data—
Thu 5 NovSokolov 20:19No data—
Wed 4 NovSokolov 20:19No data—
Tue 3 NovSokolov 20:19No data—
Mon 2 NovSokolov 20:19No data—
Sun 1 NovSokolov 20:19No data—
Sat 31 OctSokolov 20:21No data—
Fri 30 OctSokolov 20:21No data—
Thu 29 OctSokolov 20:21No data—
Wed 28 OctSokolov 20:21No data—
Tue 27 OctSokolov 20:22No data—
Mon 26 OctSokolov 20:21No data—
Sun 25 OctSokolov 20:21No data—
Sat 24 OctSokolov 20:21No data—
Fri 23 OctSokolov 20:21No data—
Thu 22 OctSokolov 20:21No data—
Wed 21 OctSokolov 20:21No data—
Tue 20 OctSokolov 20:21No data—
Mon 19 OctSokolov 20:21No data—
Sun 18 OctSokolov 20:22No data—
Sat 17 OctSokolov 20:21No data—
Fri 16 OctSokolov 20:21No data—
Thu 15 OctSokolov 20:21No data—
Wed 14 OctSokolov 20:21No data—
Tue 13 OctSokolov 20:21No data—
Mon 12 OctSokolov 20:22No data—
Sun 11 OctSokolov 20:21No data—
Sat 10 OctSokolov 20:21No data—