S25 8564 Muri AG – Brugg AG

View line S25

Muri AG 17:01 → Brugg AG 17:25 Daily 0 h 24 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Brugg AG at 17:30 +5 min

  1. Muri AG17:01
  2. Wohlen AG17:07
  3. Dottikon-Dintikon17:10
  4. Othmarsingen17:16
  5. Birr17:19
  6. Lupfig17:21
  7. Brugg AG17:25

Next service: tomorrow 17:01 from Muri AG · Thu 19 Nov

Next departure 17:01 tomorrow · Muri AG
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Brugg AG, 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 18 Nov Max en route +5 min · last fix heading to Brugg AG +5 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Brugg AG +4 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Brugg AG +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 43
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
17:01on time on time
17:07≈ on time ≈ on time
17:10≈ on time ≈ +1 min
17:13≈ on time ≈ +1 min
17:16≈ on time ≈ +1 min
17:19≈ on time ≈ +1 min
17:21≈ on time ≈ +1 min
17:25on time +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
Wed 18 NovBrugg AG 17:29+5 min+5 min
Tue 17 NovBrugg AG 17:27+1 min—
Mon 16 NovBrugg AG 17:240 min—
Sun 15 NovBrugg AG 17:240 min—
Sat 14 NovBrugg AG 17:24+1 min—
Fri 13 NovBrugg AG 17:240 min+3 min
Thu 12 NovBrugg AG 17:27+1 min+6 min
Wed 11 NovBrugg AG 17:240 min—
Tue 10 NovBrugg AG 17:240 min—
Mon 9 NovBrugg AG 17:29+4 min+4 min
Sun 8 NovBrugg AG 17:240 min—
Sat 7 NovBrugg AG 17:27+1 min+1 min
Fri 6 NovBrugg AG 17:240 min—
Thu 5 NovBrugg AG 17:240 min—
Wed 4 NovBrugg AG 17:240 min—
Tue 3 NovBrugg AG 17:27+1 min—
Mon 2 NovBrugg AG 17:240 min—
Sun 1 NovBrugg AG 17:260 min—
Sat 31 OctBrugg AG 17:26No data—
Fri 30 OctBrugg AG 17:260 min—
Thu 29 OctBrugg AG 17:27+1 min+1 min
Wed 28 OctBrugg AG 17:270 min—
Tue 27 OctBrugg AG 17:260 min—
Mon 26 OctBrugg AG 17:260 min—
Sun 25 OctBrugg AG 17:26+1 min—
Sat 24 OctBrugg AG 17:260 min—
Fri 23 OctBrugg AG 17:260 min—
Thu 22 OctBrugg AG 17:260 min—
Wed 21 OctBrugg AG 17:28+2 min+2 min
Tue 20 OctBrugg AG 17:260 min—