Os 20873 20873 Selb-Plößberg – Schirnding

View line Os 20873

Selb-Plößberg 07:44 → Schirnding 08:43 Mon, Tue, Wed, Thu, Fri 0 h 59 min · 10 stops agilis Verkehrsgesellschaft mbH & Co. KG

✓ Today’s run finished

Today, last fix heading to Schirnding at 08:44 No data

  1. Selb-Plößberg07:44
  2. Hazlov08:00
  3. Vojtanov obec08:03
  4. Františkovy Lázně-Aquaforum08:14
  5. Cheb08:20
  6. Pomezí nad Ohří z08:39
  7. Schirnding08:43

Next service: tomorrow 07:44 from Selb-Plößberg · Tue 10 Nov

Next departure 07:44 tomorrow · Selb-Plößberg
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
46%
18/39 runs under 3 min
RT coverage: 39 full · 0 partial · 25 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+9min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Schirnding, 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 23 Sept Max en route +13 min · last fix heading to — +12 min
  • Mon 5 Oct Max en route +11 min · last fix heading to — +11 min
  • Mon 17 Aug Max en route +11 min · last fix heading to — +11 min
  • Tue 25 Aug Max en route +10 min · last fix heading to — +10 min
  • Wed 30 Sept Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 46% · 18
  • 3–10 min 44% · 17
  • 10–30 min 10% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=8
  • 43% T n=7
  • 25% W n=8
  • 63% T n=8
  • 50% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
07:44+5 min +8 min
07:50 / 07:51≈ +5 min ≈ +8 min
08:00≈ +5 min ≈ +7 min
08:03≈ +5 min ≈ +7 min
08:12 / 08:13≈ +5 min ≈ +7 min
08:14≈ +5 min ≈ +8 min
08:20 / 08:31≈ +4 min ≈ +7 min
08:35≈ +3 min ≈ +8 min
08:39≈ +3 min ≈ +9 min
08:43+3 min +9 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
Mon 9 NovSchirnding 08:44No data—
Fri 6 NovSchirnding 08:44No data—
Thu 5 NovSchirnding 08:44No data—
Wed 4 NovSchirnding 08:44No data—
Tue 3 NovSchirnding 08:44No data—
Mon 2 NovSchirnding 08:44No data—
Fri 30 OctSchirnding 08:44No data—
Thu 29 OctSchirnding 08:44No data—
Wed 28 OctSchirnding 08:44No data—
Tue 27 OctSchirnding 08:44No data—
Mon 26 OctSchirnding 08:44No data—
Fri 23 OctSchirnding 08:45No data—
Thu 22 OctSchirnding 08:45No data—
Wed 21 OctSchirnding 08:44No data—
Tue 20 OctSchirnding 08:44No data—
Mon 19 OctSchirnding 08:44No data—
Fri 16 OctSchirnding 08:45No data—
Thu 15 OctSchirnding 08:44No data—
Wed 14 OctSchirnding 08:44No data—
Tue 13 OctSchirnding 08:44No data—
Mon 12 OctSchirnding 08:44No data—
Fri 9 OctSchirnding 08:44No data—
Thu 8 OctSchirnding 08:44No data—
Wed 7 OctSchirnding 08:44No data—
Tue 6 OctSchirnding 08:44No data—
Mon 5 Oct— 09:06+11 min+11 min
Fri 2 Oct— 08:59+3 min+5 min
Thu 1 Oct— 08:550 min+5 min
Wed 30 Sept— 09:04+9 min+9 min
Tue 29 Sept— 08:550 min+4 min