R12 6784 Frutigen – Spiez

View line R12

Frutigen 19:01 → Spiez 19:14 Mon, Tue, Wed, Thu, Fri 0 h 13 min · 4 stops BLS

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Monday 19:01 from Frutigen · Mon 9 Nov

Next departure 19:01 Monday · Frutigen
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 1 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: +2 min

Last 30 days

Arrival delay at Spiez, 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 2 Nov Max en route +4 min · last fix heading to Spiez +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 35
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=6
  • 100% F n=5
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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
19:01on time +1 min
19:05≈ on time ≈ +1 min
19:06≈ on time ≈ +1 min
19:14on 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
Fri 6 NovSpiez 19:140 min—
Thu 5 NovSpiez 19:140 min—
Wed 4 NovSpiez 19:140 min—
Tue 3 NovSpiez 19:140 min—
Mon 2 NovSpiez 19:19+4 min+4 min
Sun 1 NovBoudry Littorail 20:27−1 min—
Sat 31 OctBoudry Littorail 20:270 min—
Fri 30 OctSpiez 19:150 min—
Thu 29 OctSpiez 19:150 min—
Wed 28 OctSpiez 19:17+2 min+2 min
Tue 27 OctSpiez 19:16+1 min+1 min
Mon 26 OctSpiez 19:150 min—
Sun 25 OctBoudry Littorail 20:27No data—
Sat 24 OctBoudry Littorail 20:270 min—
Fri 23 OctSpiez 19:150 min—
Thu 22 OctSpiez 19:16+1 min—
Wed 21 OctSpiez 19:150 min—
Tue 20 OctSpiez 19:160 min—
Mon 19 OctSpiez 19:16+2 min+2 min
Sun 18 OctBoudry Littorail 20:280 min—
Sat 17 OctBoudry Littorail 20:28+1 min+2 min
Fri 16 OctSpiez 19:150 min—
Thu 15 OctSpiez 19:16+1 min—
Wed 14 OctSpiez 19:15+1 min—
Tue 13 OctSpiez 19:150 min—
Mon 12 OctSpiez 19:16+2 min+2 min
Sun 11 OctBoudry Littorail 20:270 min—
Sat 10 OctBoudry Littorail 20:29+1 min+1 min
Fri 9 OctSpiez 19:160 min—
Thu 8 OctSpiez 19:16+1 min—