RE12 4780 Wettingen – Olten

View line RE12

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

Running now · updated 17:45

Position estimated from the timetable

Between Wettingen and Baden 0 min

Estimated arrival at Olten 18:24 · 31 km/h

  1. Wettingen17:42
  2. Baden17:46
  3. Turgi17:51
  4. Brugg AG17:57
  5. Wildegg18:07
  6. Aarau18:13
  7. Olten18:24

Today it is running no worse than usual: typical arrival delay is +1 min; 80% of the last 30 runs arrived on time.

On-time · 30 days
80%
24/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
88%
44/50 runs under 3 min
RT coverage: 49 full · 1 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Thu 12 Nov Max en route +8 min · last fix heading to Olten +8 min
  • Tue 17 Nov Max en route +5 min · last fix heading to Olten +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Fri 23 Oct Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 44
  • 3–10 min 12% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 63% T n=8
  • 86% W n=7
  • 88% T n=8
  • 83% F n=6
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

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