R12 6764 Frutigen → Spiez

View line R12

Frutigen 09:01 → Spiez 09:14 Daily 0 h 13 min · 4 stops BLS

R12 6764 Frutigen–Spiez: final delay under 3 min on 27 of its 28 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 17:31 (GMT+1).

✓ Today’s run finished

Today it reached Spiez at 09:14 0 min

  1. Frutigen09:01
  2. Reichenbach im Kandertal09:05
  3. Mülenen09:06
  4. Spiez09:14

Next service: tomorrow 09:01 from Frutigen · Mon 23 Nov

Next departure 09:01 tomorrow · Frutigen
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
96%
48/50 runs under 3 min
RT coverage: 50 full · 0 partial · 2 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 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

  • Fri 25 Sept Max en route +4 min · last fix heading to Boudry Tuilière +4 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Boudry Littorail +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 48
  • 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
  • 100% T n=5
  • 88% F n=8
  • 86% S n=7
  • 100% S n=9

Stops and timetable

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

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