S27 8264 Ziegelbrücke – Siebnen-Wangen

View line S27

Ziegelbrücke 16:26 → Siebnen-Wangen 16:38 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 5 stops SOB

✓ Today’s run finished

Today it reached Siebnen-Wangen at 16:38 0 min

  1. Ziegelbrücke16:26
  2. Bilten16:28
  3. Reichenburg16:32
  4. Schübelbach-Buttikon16:35
  5. Siebnen-Wangen16:38

Next service: Monday 16:26 from Ziegelbrücke · Mon 23 Nov

Next departure 16:26 Monday · Ziegelbrücke
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 0 no data
On-time · 90 days
100%
35/35 runs under 3 min
RT coverage: 35 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Siebnen-Wangen, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 3% · 1
  • On time 97% · 34
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 35 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
16:26on time on time
16:28≈ on time ≈ on time
16:32≈ on time ≈ on time
16:35≈ on time ≈ on time
16:38on time on time

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 20 NovSiebnen-Wangen 16:390 min—
Thu 19 NovSiebnen-Wangen 16:390 min—
Wed 18 NovSiebnen-Wangen 16:390 min—
Tue 17 NovSiebnen-Wangen 16:390 min—
Mon 16 NovSiebnen-Wangen 16:38−1 min—
Fri 13 NovSiebnen-Wangen 16:39−1 min—
Thu 12 NovSiebnen-Wangen 16:39+1 min—
Wed 11 NovSiebnen-Wangen 16:390 min—
Tue 10 NovSiebnen-Wangen 16:390 min—
Mon 9 NovSiebnen-Wangen 16:390 min—
Fri 6 NovSiebnen-Wangen 16:38−1 min—
Thu 5 NovSiebnen-Wangen 16:38−1 min—
Wed 4 NovSiebnen-Wangen 16:38−1 min—
Tue 3 NovSiebnen-Wangen 16:390 min—
Mon 2 NovSiebnen-Wangen 16:390 min—
Fri 30 OctSiebnen-Wangen 16:40+1 min+1 min
Thu 29 OctSiebnen-Wangen 16:38−1 min—
Wed 28 OctSiebnen-Wangen 16:400 min—
Tue 27 OctSiebnen-Wangen 16:390 min—
Mon 26 OctSiebnen-Wangen 16:390 min—
Fri 23 OctSiebnen-Wangen 16:390 min—
Thu 22 OctSiebnen-Wangen 16:39−1 min—
Wed 21 OctSiebnen-Wangen 16:390 min—
Tue 20 OctSiebnen-Wangen 16:390 min—
Mon 19 OctSiebnen-Wangen 16:38−1 min—
Fri 16 OctSiebnen-Wangen 16:400 min—
Thu 15 OctSiebnen-Wangen 16:38−1 min—
Wed 14 OctSiebnen-Wangen 16:390 min—
Tue 13 OctSiebnen-Wangen 16:390 min—
Mon 12 OctSiebnen-Wangen 16:38−1 min—