RE12 4788 Wettingen – Olten

View line RE12

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

✓ Today’s run finished

Today it reached Olten at 22:24 0 min

  1. Wettingen21:42
  2. Baden21:46
  3. Turgi21:51
  4. Brugg AG21:57
  5. Wildegg22:07
  6. Aarau22:13
  7. Olten22:24

Next service: tomorrow 21:42 from Wettingen · Wed 11 Nov

Next departure 21:42 tomorrow · Wettingen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
40/42 runs under 3 min
RT coverage: 42 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

  • Sat 7 Nov Max en route +4 min · last fix heading to Olten +4 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Olten +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 40
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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