RE12 4764 Wettingen – Olten

View line RE12

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

✓ Today’s run finished

Today it reached Olten at 10:24 0 min

  1. Wettingen09:42
  2. Baden09:46
  3. Turgi09:51
  4. Brugg AG09:57
  5. Wildegg10:07
  6. Aarau10:13
  7. Olten10:24

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

Next departure 09:42 tomorrow · Wettingen
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
51/52 runs under 3 min
RT coverage: 52 full · 0 partial · 1 no data
Typical delay
0min
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

Worst days

  • Fri 16 Oct Max en route +8 min · last fix heading to Olten +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 51
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=10
  • 100% W n=8
  • 100% T n=5
  • 80% F n=5
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

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