S22 4134 Teufen AR – Speicher

View line S22

Teufen AR 13:55 → Speicher 14:31 Mon, Tue, Wed, Thu, Fri 0 h 36 min · 17 stops Appenzeller Bahnen

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 13:55 from Teufen AR · Mon 9 Nov

Next departure 13:55 Monday · Teufen AR
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
98%
42/43 runs under 3 min
RT coverage: 43 full · 0 partial · 8 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Speicher, in minutes. One bar per run.

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

Worst days

  • Fri 16 Oct Max en route +8 min · last fix heading to Speicher +7 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 95% · 41
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 100% W n=7
  • 100% T n=6
  • 86% F n=7
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 43 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
13:55on time on time
13:57≈ on time ≈ on time
13:58≈ on time ≈ +1 min
13:59≈ on time ≈ +1 min
14:01≈ on time ≈ +1 min
14:04≈ on time ≈ +1 min
14:06≈ on time ≈ +1 min
14:11≈ on time ≈ +1 min
14:13≈ on time ≈ +1 min
14:15≈ on time ≈ +1 min
14:17≈ on time ≈ +1 min
14:18≈ on time ≈ +1 min
14:20≈ on time ≈ +1 min
14:23≈ +1 min ≈ +1 min
14:26≈ +1 min ≈ +1 min
14:28≈ +1 min ≈ +2 min
14:31+1 min +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
Fri 6 NovSpeicher 14:32+1 min+1 min
Thu 5 NovSpeicher 14:32No data—
Wed 4 NovSpeicher 14:32+2 min+2 min
Tue 3 NovSpeicher 14:32+1 min+1 min
Mon 2 NovSpeicher 14:32No data—
Sun 1 NovAarau 12:52+2 min+2 min
Sat 31 OctAarau 12:51+1 min+2 min
Fri 30 OctSpeicher 14:32+1 min+2 min
Thu 29 OctSpeicher 14:32+1 min—
Wed 28 OctSpeicher 14:32+1 min+1 min
Tue 27 OctSpeicher 14:32+1 min+1 min
Mon 26 OctSpeicher 14:32No data—
Sun 25 OctAarau 12:50+1 min+2 min
Sat 24 OctAarau 12:500 min+1 min
Fri 23 OctSpeicher 14:32+1 min+1 min
Thu 22 OctSpeicher 14:32No data—
Wed 21 OctSpeicher 14:32+1 min+2 min
Tue 20 OctSpeicher 14:320 min—
Mon 19 OctSpeicher 14:32No data—
Sun 18 OctAarau 12:510 min+1 min
Sat 17 OctAarau 12:500 min+1 min
Fri 16 OctSpeicher 14:33+7 min+8 min
Thu 15 OctSpeicher 14:32No data—
Wed 14 OctSpeicher 14:32+1 min+2 min
Tue 13 OctSpeicher 14:320 min—
Mon 12 OctSpeicher 14:32No data—
Sun 11 OctAarau 12:500 min—
Sat 10 OctAarau 12:500 min—
Fri 9 OctSpeicher 14:32+1 min+2 min
Thu 8 OctSpeicher 14:320 min+1 min