RE12 4772 Wettingen – Olten

View line RE12

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

✓ Today’s run finished

Today, last fix heading to Olten at 14:24 No data

  1. Wettingen13:42
  2. Baden13:46
  3. Turgi13:51
  4. Brugg AG13:57
  5. Wildegg14:07
  6. Aarau14:13
  7. Olten14:24

Next service: tomorrow 13:42 from Wettingen · Fri 20 Nov

Next departure 13:42 tomorrow · Wettingen
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
92%
36/39 runs under 3 min
RT coverage: 39 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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 17 Oct Max en route +4 min · last fix heading to Olten +4 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Olten +3 min
  • Tue 3 Nov Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 36
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 86% T n=7
  • 86% W n=7
  • 100% T n=1
  • 100% F n=6
  • 86% S n=7
  • 100% S n=8

Stops and timetable

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

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