RE12 4768 Wettingen – Olten

View line RE12

Wettingen 11:42 → Olten 12:24 Daily 0 h 42 min · 7 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Olten at 12:24 0 min

  1. Wettingen11:42
  2. Baden11:46
  3. Turgi11:51
  4. Brugg AG11:57
  5. Wildegg12:07
  6. Aarau12:13
  7. Olten12:24

Next service: tomorrow 11:42 from Wettingen · Thu 12 Nov

Next departure 11:42 tomorrow · Wettingen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 9 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 Olten, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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:42on time on time
11:46 / 11:47≈ on time ≈ on time
11:51 / 11:52≈ on time ≈ on time
11:57 / 12:00≈ on time ≈ on time
12:07≈ on time ≈ +1 min
12:13≈ on time ≈ +1 min
12:24+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
Wed 11 NovOlten 12:240 min—
Tue 10 NovOlten 12:240 min—
Mon 9 NovOlten 12:24No data—
Sun 8 NovOlten 12:24+1 min—
Sat 7 NovOlten 12:240 min—
Fri 6 NovOlten 12:24−1 min—
Thu 5 NovOlten 12:24No data—
Wed 4 NovOlten 12:240 min—
Tue 3 NovOlten 12:240 min—
Mon 2 NovOlten 12:24No data—
Sun 1 NovOlten 12:25+1 min—
Sat 31 OctOlten 12:250 min—
Fri 30 OctOlten 12:26+1 min—
Thu 29 OctOlten 12:25No data—
Wed 28 OctOlten 12:26+1 min+1 min
Tue 27 OctOlten 12:250 min—
Mon 26 OctOlten 12:26No data—
Sun 25 OctOlten 12:26+2 min+2 min
Sat 24 OctOlten 12:26+1 min+1 min
Fri 23 OctOlten 12:26+1 min—
Thu 22 OctOlten 12:25No data—
Wed 21 OctOlten 12:26+1 min—
Tue 20 OctOlten 12:24−1 min—
Mon 19 OctOlten 12:25No data—
Sun 18 OctOlten 12:27+2 min+2 min
Sat 17 OctOlten 12:250 min—
Fri 16 OctOlten 12:27+1 min+1 min
Thu 15 OctOlten 12:25No data—
Wed 14 OctOlten 12:25+1 min—
Tue 13 OctOlten 12:250 min—