S21 2046 Speicher – Trogen

View line S21

Speicher 05:14 → Trogen 05:20 Daily 0 h 06 min · 4 stops Appenzeller Bahnen

✓ Today’s run finished

Today it reached Trogen at 05:20 −1 min

  1. Speicher05:14
  2. Bendlehn05:15
  3. Gfeld05:17
  4. Trogen05:20

Next service: tomorrow 05:14 from Speicher · Fri 20 Nov

Next departure 05:14 tomorrow · Speicher
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
97%
73/75 runs under 3 min
RT coverage: 75 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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 18 Sept Max en route +14 min · last fix heading to St. Gallen +14 min
  • Sat 5 Sept Max en route +3 min · last fix heading to Herisau +3 min

Distribution · 90 days

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

  • Early 53% · 40
  • On time 44% · 33
  • 3–10 min 1% · 1
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=10
  • 100% W n=11
  • 100% T n=11
  • 90% F n=10
  • 90% S n=10
  • 100% S n=12

Stops and timetable

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

Last 90 days, 75 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:14+1 min +1 min
05:15≈ on time ≈ on time
05:17≈ on time ≈ on time
05:201 min early +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
Thu 19 NovTrogen 05:49−1 min—
Wed 18 NovTrogen 05:49−1 min—
Tue 17 NovTrogen 05:49−1 min—
Mon 16 NovTrogen 05:49−1 min—
Sun 15 NovTrogen 05:52+1 min+1 min
Sat 14 NovTrogen 05:49−1 min—
Fri 13 NovTrogen 05:49−1 min—
Thu 12 NovHerisau 01:130 min—
Wed 11 NovTrogen 05:49−2 min—
Tue 10 NovTrogen 05:49−1 min—
Mon 9 NovTrogen 05:49−1 min—
Sun 8 NovTrogen 05:49−1 min—
Sat 7 NovTrogen 05:490 min—
Fri 6 NovTrogen 05:49−1 min—
Thu 5 NovTrogen 05:49−1 min—
Wed 4 NovTrogen 05:49−2 min—
Tue 3 NovTrogen 05:49−1 min—
Mon 2 NovTrogen 05:49−1 min—
Sun 1 NovTrogen 05:49−2 min—
Sat 31 OctTrogen 05:50−1 min—
Fri 30 OctTrogen 05:50−1 min—
Thu 29 OctTrogen 05:50−1 min—
Wed 28 OctTrogen 05:50−1 min—
Tue 27 OctTrogen 05:510 min—
Mon 26 OctTrogen 05:48−1 min—
Sun 25 OctTrogen 05:50−1 min—
Sat 24 OctTrogen 05:49−2 min—
Fri 23 OctTrogen 05:50−1 min—
Thu 22 OctTrogen 05:50−1 min—
Wed 21 OctTrogen 05:50−1 min—