RE12 4758 Wettingen – Olten

View line RE12

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

✓ Today’s run finished

Today it reached Olten at 07:29 +5 min

  1. Wettingen06:42
  2. Baden06:46
  3. Turgi06:51
  4. Brugg AG06:57
  5. Wildegg07:07
  6. Aarau07:13
  7. Olten07:24

Next service: tomorrow 06:42 from Wettingen · Wed 18 Nov

Next departure 06:42 tomorrow · Wettingen
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 26 Oct Max en route +6 min · last fix heading to Olten +6 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Olten +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 43
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 86% T n=7
  • 100% W n=6
  • 100% T n=6
  • 100% F n=6
  • 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, 45 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
06:42on time on time
06:46 / 06:47≈ on time ≈ on time
06:51 / 06:52≈ on time ≈ on time
06:57 / 07:00≈ on time ≈ +1 min
07:07≈ on time ≈ +1 min
07:13≈ +1 min ≈ +2 min
07:24+1 min +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
Tue 17 NovOlten 07:29+5 min+5 min
Mon 16 NovOlten 07:27+2 min+2 min
Sun 15 NovOlten 07:240 min—
Sat 14 NovOlten 07:27+2 min+2 min
Fri 13 NovOlten 07:240 min—
Thu 12 NovOlten 07:24+1 min—
Wed 11 NovOlten 07:27+2 min+2 min
Tue 10 NovOlten 07:27+2 min+2 min
Mon 9 NovOlten 07:27+2 min+2 min
Sun 8 NovOlten 07:240 min—
Sat 7 NovOlten 07:240 min—
Fri 6 NovOlten 07:240 min—
Thu 5 NovOlten 07:240 min—
Wed 4 NovOlten 07:240 min—
Tue 3 NovOlten 07:240 min—
Mon 2 NovOlten 07:24−1 min—
Sun 1 NovOlten 07:26+1 min—
Sat 31 OctOlten 07:26+1 min—
Fri 30 OctOlten 07:26+1 min+1 min
Thu 29 OctOlten 07:26+1 min—
Wed 28 OctOlten 07:26+1 min+1 min
Tue 27 OctOlten 07:26+1 min—
Mon 26 OctOlten 07:32+6 min+6 min
Sun 25 OctOlten 07:25+1 min—
Sat 24 OctOlten 07:26+1 min+1 min
Fri 23 OctOlten 07:26+1 min—
Thu 22 OctOlten 07:27+2 min+2 min
Wed 21 OctOlten 07:26+1 min+1 min
Tue 20 OctOlten 07:28+2 min+2 min
Mon 19 OctOlten 07:26+1 min—