R32 2415 Lenk im Simmental → Zweisimmen

View line R32

Lenk im Simmental 10:05 → Zweisimmen 10:24 Sat, Sun 0 h 19 min · 7 stops MOB

R32 2415 Lenk im Simmental–Zweisimmen: final delay under 3 min on 3 of its 3 runs with data in the last 30 days (100%). TrainsRadar data as of 21 Nov 2026, 13:23 (GMT+1).

✓ Today’s run finished

Today it reached Zweisimmen at 10:25 +1 min

  1. Lenk im Simmental10:05
  2. Boden10:07
  3. Matten i.S.10:10
  4. St. Stephan10:14
  5. Stöckli10:17
  6. Blankenburg10:20
  7. Zweisimmen10:24

Next service: tomorrow 10:05 from Lenk im Simmental · Sun 22 Nov

Next departure 10:05 tomorrow · Lenk im Simmental
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 6 no data
On-time · 90 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 8 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Zweisimmen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 7 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
10:05on time on time
10:07≈ on time ≈ on time
10:10≈ on time ≈ on time
10:14 / 10:15≈ on time ≈ +1 min
10:17≈ on time ≈ +1 min
10:20≈ +1 min ≈ +1 min
10: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
Sat 21 NovZweisimmen 10:24+1 min—
Sun 15 NovZweisimmen 10:24No data—
Sat 14 NovZweisimmen 10:24No data—
Sun 8 NovZweisimmen 10:24No data—
Sat 7 NovZweisimmen 10:24No data—
Sun 1 NovZweisimmen 10:25No data—
Sat 31 OctZweisimmen 10:25No data—
Sun 25 OctZweisimmen 10:24+1 min—
Sat 24 OctZweisimmen 10:27+2 min+2 min
Sun 18 OctZweisimmen 10:26No data—
Sat 17 OctZweisimmen 10:26+1 min+3 min
Sun 11 OctZweisimmen 10:24+1 min—
Sat 10 OctZweisimmen 10:27+2 min+2 min
Mon 5 OctZweisimmen 10:26No data—
Sun 4 OctZweisimmen 10:26+1 min—