R62 159 Interlaken Ost – Lauterbrunnen

View line R62

Interlaken Ost 12:04 → Lauterbrunnen 12:26 Daily 0 h 22 min · 5 stops BOB (Berner Oberland-Bahnen)

Running now · updated 12:15

Position estimated from the timetable

Between Wilderswil and Zweilütschinen No data

Estimated arrival at Lauterbrunnen 12:26 · 45 km/h

  1. Interlaken Ost12:04
  2. Matten b. Interlaken12:06
  3. Wilderswil12:09
  4. Zweilütschinen12:16
  5. Lauterbrunnen12:26
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
95%
57/60 runs under 3 min
RT coverage: 60 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

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

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

Worst days

  • Wed 7 Oct Max en route +43 min · last fix heading to Bercher +43 min
  • Tue 20 Oct Max en route +42 min · last fix heading to Bercher +42 min
  • Tue 17 Nov Max en route +6 min · last fix heading to Morges +4 min

Distribution · 90 days

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

  • Early 28% · 17
  • On time 67% · 40
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 3% · 2

On-time by weekday

  • 100% M n=8
  • 80% T n=10
  • 89% W n=9
  • 100% T n=8
  • 100% F n=9
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 60 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 10Today
12:04on time on timePassed
12:06 / 12:07≈ on time ≈ on timePassed
12:09 / 12:10≈ on time ≈ on timePassed
12:16 / 12:17≈ on time ≈ +1 minNext
12:26on 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 NovZweilütschinen 12:14Partial coverageNo data—
Wed 18 NovMorges 20:02−2 min+5 min
Tue 17 NovMorges 20:09+4 min+6 min
Mon 16 NovMorges 20:03−2 min+6 min
Sun 15 NovBercher 19:370 min+2 min
Sat 14 NovBercher 19:380 min+3 min
Fri 13 NovMorges 20:04+3 min+4 min
Thu 12 NovMorges 20:04−1 min+6 min
Wed 11 NovMorges 20:040 min+4 min
Tue 10 NovMorges 20:03−2 min+5 min
Mon 9 NovMorges 20:02−2 min+4 min
Sun 8 NovBercher 19:37−1 min—
Sat 7 NovBercher 19:37+1 min+2 min
Fri 6 NovMorges 20:040 min+4 min
Thu 5 NovMorges 20:04−1 min+3 min
Wed 4 NovMorges 20:04+1 min+6 min
Tue 3 NovMorges 20:040 min+5 min
Mon 2 NovMorges 20:04−1 min+3 min
Sun 1 NovBercher 19:38+1 min+1 min
Sat 31 OctBercher 19:380 min+2 min
Fri 30 OctMorges 20:030 min+4 min
Thu 29 OctMorges 20:03−2 min+2 min
Wed 28 OctMorges 20:03−2 min+3 min
Tue 27 OctMorges 20:07+2 min+12 min
Mon 26 OctMorges 20:03−2 min+4 min
Sun 25 OctBercher 19:37−1 min+1 min
Sat 24 OctBercher 19:38+1 min+6 min
Fri 23 OctMorges 20:03−1 min+4 min
Thu 22 OctMorges 20:04−1 min+4 min
Wed 21 OctMorges 20:02−2 min+4 min