R70 9067 Interlaken Ost – Meiringen

View line R70

Interlaken Ost 10:33 → Meiringen 11:06 Daily 0 h 33 min · 9 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Meiringen at 11:08 +2 min

  1. Interlaken Ost10:33
  2. Ringgenberg10:36
  3. Oberried am Brienzersee10:44
  4. Ebligen10:47
  5. Brienz West10:50
  6. Brienzwiler10:58
  7. Meiringen11:06

Next service: tomorrow 10:33 from Interlaken Ost · Fri 20 Nov

Next departure 10:33 tomorrow · Interlaken Ost
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 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: 0 min

Last 30 days

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

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

Worst days

  • Thu 15 Oct Max en route +5 min · last fix heading to Zermatt +5 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Zermatt +3 min

Distribution · 90 days

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

  • Early 9% · 4
  • On time 87% · 41
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 71% T n=7
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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:33on time on time
10:36≈ on time ≈ on time
10:39≈ on time ≈ on time
10:44≈ on time ≈ on time
10:47≈ on time ≈ +1 min
10:50≈ on time ≈ +1 min
10:53≈ on time ≈ +1 min
10:58≈ on time ≈ +1 min
11:06on 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 NovMeiringen 11:07+2 min+2 min
Wed 18 NovMeiringen 11:040 min+2 min
Tue 17 NovMeiringen 11:050 min—
Mon 16 NovMeiringen 11:040 min+1 min
Sun 15 NovMeiringen 11:040 min—
Sat 14 NovMeiringen 11:040 min—
Fri 13 NovMeiringen 11:070 min—
Thu 12 NovMeiringen 11:070 min—
Wed 11 NovMeiringen 11:040 min—
Tue 10 NovMeiringen 11:04−1 min—
Mon 9 NovMeiringen 11:070 min—
Sun 8 NovZermatt 12:590 min—
Sat 7 NovZermatt 12:540 min—
Fri 6 NovZermatt 12:580 min—
Thu 5 NovZermatt 12:580 min—
Wed 4 NovZermatt 12:57−1 min—
Tue 3 NovZermatt 12:570 min+1 min
Mon 2 NovZermatt 12:580 min+1 min
Sun 1 NovZermatt 12:570 min—
Sat 31 OctZermatt 12:560 min+1 min
Fri 30 OctZermatt 12:57−1 min—
Thu 29 OctZermatt 12:58+1 min+1 min
Wed 28 OctZermatt 12:580 min—
Tue 27 OctZermatt 12:570 min—
Mon 26 OctZermatt 12:580 min—
Sun 25 OctZermatt 12:57−1 min—
Sat 24 OctZermatt 12:56−1 min+1 min
Fri 23 OctZermatt 12:580 min—
Thu 22 OctZermatt 12:58+3 min+3 min
Wed 21 OctZermatt 12:56−1 min+2 min