R32 2431 Lenk im Simmental – Gstaad

View line R32

Lenk im Simmental 18:05 → Gstaad 18:55 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 10 stops MOB

✓ Today’s run finished

Today it reached Gstaad at 18:56 +1 min

  1. Lenk im Simmental18:05
  2. Matten i.S.18:10
  3. St. Stephan18:14
  4. Blankenburg18:20
  5. Zweisimmen18:24
  6. Schönried18:46
  7. Gstaad18:55

Next service: tomorrow 18:05 from Lenk im Simmental · Fri 20 Nov

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

Last 30 days

Arrival delay at Gstaad, 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

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

  • Early 5% · 1
  • On time 95% · 20
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 21 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
18:05on time on time
18:07≈ on time ≈ on time
18:10≈ on time ≈ on time
18:14 / 18:15≈ on time ≈ on time
18:17≈ on time ≈ on time
18:20≈ on time ≈ on time
18:24 / 18:28≈ on time ≈ on time
18:43≈ on time ≈ on time
18:46≈ on time ≈ on time
18:55on time +1 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 NovGstaad 18:57+1 min—
Wed 18 NovGstaad 18:540 min—
Tue 17 NovGstaad 18:540 min—
Mon 16 NovGstaad 18:540 min—
Fri 13 NovGstaad 18:54No data—
Thu 12 NovGstaad 18:54No data—
Wed 11 NovGstaad 18:54No data—
Tue 10 NovGstaad 18:54No data—
Mon 9 NovGstaad 18:54No data—
Fri 6 NovGstaad 18:54No data—
Thu 5 NovGstaad 18:54No data—
Wed 4 NovGstaad 18:54No data—
Tue 3 NovGstaad 18:54No data—
Mon 2 NovGstaad 18:54No data—
Fri 30 OctGstaad 18:56No data—
Thu 29 OctGstaad 18:56No data—
Wed 28 OctGstaad 18:55−1 min—
Tue 27 OctGstaad 18:560 min—
Mon 26 OctGstaad 18:56−1 min—
Fri 23 OctGstaad 18:560 min—
Thu 22 OctGstaad 18:57+1 min—
Wed 21 OctGstaad 18:57+1 min+1 min
Tue 20 OctGstaad 18:560 min—
Mon 19 OctGstaad 18:560 min—
Fri 16 OctGstaad 18:560 min+1 min
Thu 15 OctGstaad 18:560 min—
Wed 14 OctGstaad 18:560 min—
Tue 13 OctGstaad 18:56No data—
Mon 12 OctGstaad 18:560 min—
Fri 9 OctGstaad 18:570 min—