Os 17223 17223 Hranice v Čechách – Aš

View line Os 17223

Hranice v Čechách 17:08 → Aš 17:37 Daily 0 h 29 min · 7 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 17:08 from Hranice v Čechách · Mon 9 Nov

Next departure 17:08 today · Hranice v Čechách
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
98%
53/54 runs under 3 min
RT coverage: 54 full · 0 partial · 35 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 Aš, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 20 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 53
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 54 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
17:08on time on time
17:15≈ on time ≈ on time
17:21≈ on time ≈ +1 min
17:24≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:32 / 17:33≈ on time ≈ +2 min
17:37on 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 8 NovAš 17:38No data—
Sat 7 NovAš 17:38No data—
Fri 6 NovAš 17:38No data—
Thu 5 NovAš 17:38No data—
Wed 4 NovAš 17:38No data—
Tue 3 NovAš 17:38No data—
Mon 2 NovAš 17:38No data—
Sun 1 NovAš 17:38No data—
Sat 31 OctAš 17:38No data—
Fri 30 OctAš 17:38No data—
Thu 29 OctAš 17:38No data—
Wed 28 OctAš 17:38No data—
Tue 27 OctAš 17:38No data—
Mon 26 OctAš 17:38No data—
Sun 25 OctAš 17:38No data—
Sat 24 OctAš 17:38No data—
Fri 23 OctAš 17:38No data—
Thu 22 OctAš 17:38No data—
Wed 21 OctAš 17:38No data—
Tue 20 OctAš 17:39No data—
Mon 19 OctAš 17:38No data—
Sun 18 OctAš 17:38No data—
Sat 17 OctAš 17:38No data—
Fri 16 OctAš 17:38No data—
Thu 15 OctAš 17:38No data—
Wed 14 OctAš 17:38No data—
Tue 13 OctAš 17:38No data—
Mon 12 OctAš 17:39No data—
Sun 11 OctAš 17:38No data—
Sat 10 OctAš 17:38No data—