S22 4114 Teufen AR – Trogen

View line S22

Teufen AR 11:55 → Trogen 12:37 Mon, Tue, Wed, Thu, Fri 0 h 42 min · 20 stops Appenzeller Bahnen

✓ Today’s run finished

Today it reached Trogen at 12:37 −1 min

  1. Teufen AR11:55
  2. Niederteufen11:59
  3. St. Gallen Güterbahnhof12:06
  4. St. Gallen Schülerhaus12:17
  5. Schwarzer Bären12:23
  6. Speicher12:31
  7. Trogen12:37

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

Next departure 11:55 Monday · Teufen AR
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Trogen, 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 23 Oct Max en route +4 min · last fix heading to Trogen +4 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Trogen +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 91% · 41
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=8
  • 88% W n=8
  • 100% T n=6
  • 83% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 45 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
11:55on time on time
11:57≈ on time ≈ on time
11:58≈ on time ≈ on time
11:59≈ on time ≈ on time
12:01≈ on time ≈ on time
12:04≈ on time ≈ on time
12:06≈ on time ≈ on time
12:11≈ on time ≈ +1 min
12:13≈ on time ≈ +1 min
12:15≈ on time ≈ +1 min
12:17≈ on time ≈ +1 min
12:18≈ on time ≈ +1 min
12:20≈ on time ≈ +1 min
12:23≈ on time ≈ +1 min
12:26≈ on time ≈ +1 min
12:28≈ on time ≈ +1 min
12:31≈ on time ≈ +1 min
12:32≈ on time ≈ +1 min
12:34≈ +1 min ≈ +1 min
12:37+1 min +1 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 NovTrogen 12:37−1 min—
Thu 5 NovTrogen 12:38+2 min+2 min
Wed 4 NovTrogen 12:380 min+2 min
Tue 3 NovTrogen 12:380 min+1 min
Mon 2 NovTrogen 12:37−1 min+2 min
Sun 1 NovAarau 07:500 min+1 min
Sat 31 OctAarau 07:500 min—
Fri 30 OctTrogen 12:39+1 min+2 min
Thu 29 OctTrogen 12:38+1 min—
Wed 28 OctTrogen 12:39+1 min+2 min
Tue 27 OctTrogen 12:390 min+2 min
Mon 26 OctTrogen 12:38+2 min+2 min
Sun 25 OctAarau 07:500 min+1 min
Sat 24 OctAarau 07:500 min—
Fri 23 OctTrogen 12:42+4 min+4 min
Thu 22 OctTrogen 12:38+1 min+2 min
Wed 21 OctTrogen 12:380 min+1 min
Tue 20 OctTrogen 12:40+1 min+1 min
Mon 19 OctTrogen 12:38+1 min+1 min
Sun 18 OctAarau 07:500 min—
Sat 17 OctAarau 07:510 min+2 min
Fri 16 OctTrogen 12:380 min+2 min
Thu 15 OctTrogen 12:38+1 min+1 min
Wed 14 OctTrogen 12:37−1 min+2 min
Tue 13 OctTrogen 12:38−1 min+2 min
Mon 12 OctTrogen 12:38No data—
Sun 11 OctAarau 07:500 min—
Sat 10 OctAarau 07:500 min—
Fri 9 OctTrogen 12:39+1 min+1 min
Thu 8 OctTrogen 12:40+1 min+2 min