Os 17241 17241 Aš město – Aš

View line Os 17241

Aš město 05:38 → Aš 05:42 Mon, Tue, Wed, Thu, Fri 0 h 04 min · 2 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Aš at 05:43 No data

  1. Aš město05:38
  2. Aš05:42

Next service: Monday 05:38 from Aš město · Mon 9 Nov

Full trip card
Next departure 05:38 Monday · Aš město
On-time · 30 days
—
Too little data (0/22 runs with data)
RT coverage: 0 full · 0 partial · 22 no data
On-time · 90 days
83%
34/41 runs under 3 min
RT coverage: 41 full · 0 partial · 24 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 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

  • Mon 24 Aug Max en route +11 min · last fix heading to — +11 min
  • Mon 28 Sept Max en route +6 min · last fix heading to — +5 min
  • Wed 23 Sept Max en route +4 min · last fix heading to — +4 min
  • Fri 4 Sept Max en route +4 min · last fix heading to — +4 min
  • Thu 3 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 34
  • 3–10 min 15% · 6
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 78% M n=9
  • 88% T n=8
  • 88% W n=8
  • 88% T n=8
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 41 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
Aš město
05:38on time +4 min
Aš
05:42on 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
Fri 6 NovAš 05:43No data—
Thu 5 NovAš 05:43No data—
Wed 4 NovAš 05:43No data—
Tue 3 NovAš 05:44No data—
Mon 2 NovAš 05:43No data—
Fri 30 OctAš 05:43No data—
Thu 29 OctAš 05:43No data—
Wed 28 OctAš 05:44No data—
Tue 27 OctAš 05:43No data—
Mon 26 OctAš 05:43No data—
Fri 23 OctAš 05:43No data—
Thu 22 OctAš 05:43No data—
Wed 21 OctAš 05:43No data—
Tue 20 OctAš 05:43No data—
Mon 19 OctAš 05:43No data—
Fri 16 OctAš 05:43No data—
Thu 15 OctAš 05:43No data—
Wed 14 OctAš 05:43No data—
Tue 13 OctAš 05:43No data—
Mon 12 OctAš 05:43No data—
Fri 9 OctAš 05:43No data—
Thu 8 OctAš 05:43No data—
Wed 7 OctAš 05:43No data—
Tue 6 OctAš 05:44No data—
Mon 5 Oct— 05:570 min—
Fri 2 Oct— 05:560 min—
Thu 1 Oct— 05:560 min—
Wed 30 Sept— 05:560 min—
Tue 29 Sept— 05:560 min—
Mon 28 Sept— 06:02+5 min+6 min