Os 20871 20871 Selb-Plößberg – Schirnding

View line Os 20871

Selb-Plößberg 05:33 → Schirnding 06:43 Mon, Tue, Wed, Thu, Fri 1 h 10 min · 10 stops agilis Verkehrsgesellschaft mbH & Co. KG

✓ Today’s run finished

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

  1. Selb-Plößberg05:33
  2. Hazlov05:55
  3. Vojtanov obec05:59
  4. Františkovy Lázně-Aquaforum06:10
  5. Cheb06:16
  6. Pomezí nad Ohří z06:39
  7. Schirnding06:43

Next service: tomorrow 05:33 from Selb-Plößberg · Tue 10 Nov

Next departure 05:33 tomorrow · Selb-Plößberg
On-time · 30 days
—
Too little data (0/26 runs with data)
RT coverage: 0 full · 0 partial · 26 no data
On-time · 90 days
79%
37/47 runs under 3 min
RT coverage: 47 full · 0 partial · 30 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 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 9 Sept Max en route +20 min · last fix heading to — +20 min
  • Tue 15 Sept Max en route +6 min · last fix heading to — +6 min
  • Mon 31 Aug Max en route +6 min · last fix heading to — +5 min
  • Thu 10 Sept Max en route +9 min · last fix heading to — +4 min
  • Mon 24 Aug Max en route +9 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 37
  • 3–10 min 19% · 9
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 38% M n=8
  • 86% T n=7
  • 88% W n=8
  • 63% T n=8
  • 100% F n=8
  • — S n=0
  • 100% S n=8

Stops and timetable

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

Last 90 days, 47 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
05:33+1 min +5 min
05:40 / 05:46≈ +2 min ≈ +5 min
05:55 / 05:56≈ +1 min ≈ +4 min
05:59≈ +1 min ≈ +4 min
06:08 / 06:09≈ +1 min ≈ +4 min
06:10≈ +1 min ≈ +4 min
06:16 / 06:31≈ +1 min ≈ +4 min
06:35≈ on time ≈ +4 min
06:39≈ on time ≈ +4 min
06:43on 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
Mon 9 NovSchirnding 06:44No data—
Sun 8 NovSchirnding 06:44No data—
Fri 6 NovSchirnding 06:44No data—
Thu 5 NovSchirnding 06:44No data—
Wed 4 NovSchirnding 06:44No data—
Tue 3 NovSchirnding 06:44No data—
Mon 2 NovSchirnding 06:44No data—
Sun 1 NovSchirnding 06:44No data—
Fri 30 OctSchirnding 06:44No data—
Thu 29 OctSchirnding 06:44No data—
Wed 28 OctSchirnding 06:44No data—
Tue 27 OctSchirnding 06:44No data—
Mon 26 OctSchirnding 06:44No data—
Sun 25 OctSchirnding 06:44No data—
Fri 23 OctSchirnding 06:44No data—
Thu 22 OctSchirnding 06:44No data—
Wed 21 OctSchirnding 06:44No data—
Tue 20 OctSchirnding 06:44No data—
Mon 19 OctSchirnding 06:44No data—
Sun 18 OctSchirnding 06:44No data—
Fri 16 OctSchirnding 06:44No data—
Thu 15 OctSchirnding 06:44No data—
Wed 14 OctSchirnding 06:44No data—
Tue 13 OctSchirnding 06:44No data—
Mon 12 OctSchirnding 06:44No data—
Sun 11 OctSchirnding 06:44No data—
Fri 9 OctSchirnding 06:44No data—
Thu 8 OctSchirnding 06:44No data—
Wed 7 OctSchirnding 06:44No data—
Tue 6 OctSchirnding 06:44No data—