Os 20889 20889 Selb-Plößberg – Aš

View line Os 20889

Selb-Plößberg 23:00 → Aš 23:07 Daily 0 h 07 min · 2 stops agilis Verkehrsgesellschaft mbH & Co. KG

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 23:00 from Selb-Plößberg · Sun 8 Nov

Next departure 23:00 today · Selb-Plößberg
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
96%
53/55 runs under 3 min
RT coverage: 55 full · 0 partial · 34 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
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 16 Aug Max en route +42 min · last fix heading to — +42 min
  • Thu 17 Sept Max en route +9 min · last fix heading to — +9 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 96% · 53
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=8
  • 88% 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 (2 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
23:001 min early on time
23:071 min early on time

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
Sat 7 NovAš 23:08No data—
Fri 6 NovAš 23:08No data—
Thu 5 NovAš 23:08No data—
Wed 4 NovAš 23:08No data—
Tue 3 NovAš 23:08No data—
Mon 2 NovAš 23:08No data—
Sun 1 NovAš 23:08No data—
Sat 31 OctAš 23:08No data—
Fri 30 OctAš 23:08No data—
Thu 29 OctAš 23:08No data—
Wed 28 OctAš 23:08No data—
Tue 27 OctAš 23:09No data—
Mon 26 OctAš 23:08No data—
Sun 25 OctAš 23:08No data—
Sat 24 OctAš 23:08No data—
Fri 23 OctAš 23:08No data—
Thu 22 OctAš 23:08No data—
Wed 21 OctAš 23:08No data—
Tue 20 OctAš 23:08No data—
Mon 19 OctAš 23:09No data—
Sun 18 OctAš 23:08No data—
Sat 17 OctAš 23:08No data—
Fri 16 OctAš 23:08No data—
Thu 15 OctAš 23:08No data—
Wed 14 OctAš 23:08No data—
Tue 13 OctAš 23:08No data—
Mon 12 OctAš 23:08No data—
Sun 11 OctAš 23:08No data—
Sat 10 OctAš 23:08No data—
Fri 9 OctAš 23:08No data—