R71 9103 Innertkirchen Kraftwerk (Bahn) – Meiringen

View line R71

Innertkirchen Kraftwerk (Bahn) 06:23 → Meiringen 06:34 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 6 stops zb Zentralbahn

✓ Today’s run finished

Today it reached Meiringen at 06:34 −2 min

  1. Innertkirchen Kraftwerk (Bahn)06:23
  2. Innertkirchen Grimseltor06:24
  3. Innertkirchen Unterwasser06:25
  4. Aareschlucht West06:29
  5. Meiringen Alpbach06:30
  6. Meiringen06:34

Next service: Monday 06:23 from Innertkirchen Kraftwerk (Bahn) · Mon 23 Nov

Next departure 06:23 Monday · Innertkirchen Kraftwerk (Bahn)
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
46/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
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 8 Oct Max en route +10 min · last fix heading to Unterzollikofen +10 min

Distribution · 90 days

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

  • Early 19% · 9
  • On time 79% · 37
  • 3–10 min 2% · 1
  • 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
  • 86% T n=7
  • 100% F n=7
  • 100% S n=6
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
06:23on time +1 min
06:24≈ on time ≈ +1 min
06:25≈ on time ≈ +1 min
06:29≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:34on 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
Fri 20 NovMeiringen 06:33−2 min—
Thu 19 NovUnterzollikofen 10:27−2 min—
Wed 18 NovUnterzollikofen 10:270 min—
Tue 17 NovUnterzollikofen 10:27+1 min—
Mon 16 NovUnterzollikofen 10:270 min—
Sun 15 NovUnterzollikofen 10:270 min—
Sat 14 NovUnterzollikofen 10:270 min—
Fri 13 NovUnterzollikofen 10:28+1 min+4 min
Thu 12 NovUnterzollikofen 10:28+1 min—
Wed 11 NovUnterzollikofen 10:28+1 min—
Tue 10 NovUnterzollikofen 10:28+2 min+2 min
Mon 9 NovUnterzollikofen 10:240 min—
Sun 8 NovZermatt 18:540 min—
Sat 7 NovZermatt 18:540 min—
Fri 6 NovZermatt 18:57−1 min—
Thu 5 NovZermatt 18:570 min+2 min
Wed 4 NovZermatt 18:540 min+1 min
Tue 3 NovZermatt 18:540 min—
Mon 2 NovZermatt 18:57−2 min—
Sun 1 NovZermatt 18:590 min—
Sat 31 OctZermatt 18:580 min—
Fri 30 OctZermatt 18:57−1 min—
Thu 29 OctZermatt 18:580 min—
Wed 28 OctZermatt 18:570 min—
Tue 27 OctZermatt 18:57−2 min—
Mon 26 OctBern 11:01+1 min+1 min
Sun 25 OctZermatt 18:56−2 min—
Sat 24 OctZermatt 18:560 min+2 min
Fri 23 OctZermatt 18:57−1 min—
Thu 22 OctZermatt 18:560 min—