R62 176 Lauterbrunnen – Interlaken Ost

View line R62

Lauterbrunnen 20:01 → Interlaken Ost 20:24 Daily 0 h 23 min · 5 stops BOB (Berner Oberland-Bahnen)

Running now · updated 20:25

Between Matten b. Interlaken and Interlaken Ost No data

Estimated arrival at Interlaken Ost 20:24 · 6 km/h

  1. Lauterbrunnen20:01
  2. Zweilütschinen20:10
  3. Wilderswil20:16
  4. Matten b. Interlaken20:18
  5. Interlaken Ost20:24
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
97%
66/68 runs under 3 min
RT coverage: 68 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Interlaken Ost, in minutes. One bar per run.

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

Worst days

  • Tue 15 Sept Max en route +13 min · last fix heading to Serocca +12 min
  • Mon 7 Sept Max en route +6 min · last fix heading to Sorengo +3 min

Distribution · 90 days

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

  • Early 31% · 21
  • On time 66% · 45
  • 3–10 min 1% · 1
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 68 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
20:01on time +1 minPassed
20:10 / 20:11≈ on time ≈ +1 minPassed
20:16 / 20:17≈ on time ≈ +1 minPassed
20:18 / 20:19≈ on time ≈ +1 minPassed
20:24on time +1 minNext

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 5 NovInterlaken Ost 20:240 min—
Wed 4 NovLausanne-Flon 00:04−2 min+3 min
Tue 3 NovLausanne-Flon 00:04−2 min+2 min
Mon 2 NovLausanne-Flon 00:040 min+1 min
Sun 1 NovEchallens 23:340 min—
Sat 31 OctLausanne-Flon 00:040 min—
Fri 30 OctLausanne-Flon 00:040 min—
Thu 29 OctLausanne-Flon 00:04−2 min+4 min
Wed 28 OctLausanne-Flon 00:04−2 min—
Tue 27 OctLausanne-Flon 00:04−2 min+1 min
Mon 26 OctLausanne-Flon 00:060 min+2 min
Sun 25 OctLausanne-Flon 00:06No data—
Sat 24 OctLausanne-Flon 00:03−2 min+2 min
Fri 23 OctLausanne-Flon 00:05−1 min+1 min
Thu 22 OctLausanne-Flon 00:060 min+1 min
Wed 21 OctLausanne-Flon 00:060 min—
Tue 20 OctLausanne-Flon 00:040 min—
Mon 19 OctLausanne-Flon 00:060 min—
Sun 18 OctLausanne-Flon 00:06+1 min+2 min
Sat 17 OctLausanne-Flon 00:06−1 min+1 min
Fri 16 OctLausanne-Flon 00:04−2 min+5 min
Thu 15 OctLausanne-Flon 00:06−1 min—
Wed 14 OctLausanne-Flon 00:05−2 min+2 min
Tue 13 OctLausanne-Flon 00:06+1 min+1 min
Mon 12 OctLausanne-Flon 00:03−3 min—
Sun 11 OctLausanne-Flon 00:04−2 min+4 min
Sat 10 OctLausanne-Flon 00:04−2 min—
Fri 9 OctLausanne-Flon 00:070 min+1 min
Thu 8 OctLausanne-Flon 00:04−2 min+1 min
Wed 7 OctCheseaux 23:480 min—