R31 2509 Lenk im Simmental → Zweisimmen

View line R31

Lenk im Simmental 06:35 → Zweisimmen 06:54 Daily 0 h 19 min · 7 stops MOB

R31 2509 Lenk im Simmental–Zweisimmen: final delay under 3 min on 26 of its 27 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 15:25 (GMT+1).

✓ Today’s run finished

Today it reached Zweisimmen at 06:54 0 min

  1. Lenk im Simmental06:35
  2. Boden06:37
  3. Matten i.S.06:40
  4. St. Stephan06:44
  5. Stöckli06:46
  6. Blankenburg06:49
  7. Zweisimmen06:54

Next service: tomorrow 06:35 from Lenk im Simmental · Sun 22 Nov

Next departure 06:35 tomorrow · Lenk im Simmental
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 49 full · 0 partial · 4 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: +1 min

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

Worst days

  • Mon 12 Oct Max en route +8 min · last fix heading to Luzern +8 min
  • Wed 18 Nov Max en route +7 min · last fix heading to Nancy +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 47
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 49 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
06:35on time on time
06:37≈ on time ≈ on time
06:40≈ on time ≈ on time
06:44≈ on time ≈ +1 min
06:46≈ on time ≈ +1 min
06:49≈ on time ≈ +1 min
06:54on 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
Sat 21 NovZweisimmen 06:530 min—
Fri 20 NovNancy 15:44+1 min+2 min
Thu 19 NovNancy 15:440 min—
Wed 18 NovNancy 15:44+7 min+7 min
Tue 17 NovNancy 15:44+2 min+2 min
Mon 16 NovNancy 15:440 min—
Sun 15 NovLuzern 09:03+1 min—
Sat 14 NovZweisimmen 06:54No data—
Fri 13 NovNancy 15:44+1 min+1 min
Thu 12 NovNancy 15:44+1 min+1 min
Wed 11 NovNancy 15:440 min—
Tue 10 NovNancy 15:44+1 min+1 min
Mon 9 NovNancy 15:440 min—
Sun 8 NovLuzern 09:020 min+6 min
Sat 7 NovZweisimmen 06:54No data—
Fri 6 NovNancy 15:440 min—
Thu 5 NovNancy 15:440 min—
Wed 4 NovNancy 15:44+1 min+1 min
Tue 3 NovNancy 15:440 min—
Mon 2 NovNancy 15:440 min—
Sun 1 NovLuzern 09:020 min—
Sat 31 OctZweisimmen 06:55No data—
Fri 30 OctLuzern 09:020 min—
Thu 29 OctLuzern 09:020 min—
Wed 28 OctLuzern 09:04+1 min+1 min
Tue 27 OctLuzern 09:03+1 min+2 min
Mon 26 OctLuzern 09:030 min—
Sun 25 OctLuzern 09:180 min—
Sat 24 OctZweisimmen 06:56+1 min+1 min
Fri 23 OctLuzern 09:03+1 min—