R11 6835 Spiez – Zweisimmen

View line R11

Spiez 19:12 → Zweisimmen 19:59 Daily 0 h 47 min · 14 stops BLS

✓ Today’s run finished

Today it reached Zweisimmen at 19:59 −2 min

  1. Spiez19:12
  2. Eifeld19:15
  3. Burgholz19:22
  4. Ringoldingen19:30
  5. Weissenburg19:36
  6. Enge im Simmental19:42
  7. Zweisimmen19:59

Next service: tomorrow 19:12 from Spiez · Sun 8 Nov

Next departure 19:12 tomorrow · Spiez
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 3 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 3 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Zweisimmen, 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 +20 min · last fix heading to Zweisimmen +19 min

Distribution · 90 days

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

  • Early 47% · 16
  • On time 50% · 17
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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:12on time on time
19:14≈ on time ≈ on time
19:15≈ on time ≈ on time
19:19≈ on time ≈ on time
19:22≈ on time ≈ on time
19:24≈ on time ≈ on time
19:28 / 19:29≈ on time ≈ on time
19:30 / 19:31≈ on time ≈ on time
19:35≈ on time ≈ +1 min
19:36≈ 1 min early ≈ +1 min
19:41≈ 1 min early ≈ +1 min
19:42≈ 1 min early ≈ +1 min
19:48 / 19:49≈ 1 min early ≈ +1 min
19:591 min early +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
Sat 7 NovZweisimmen 19:58−2 min—
Fri 6 NovZweisimmen 19:590 min—
Thu 5 NovZweisimmen 19:590 min—
Wed 4 NovZweisimmen 19:59No data—
Tue 3 NovZweisimmen 19:59−1 min—
Mon 2 NovZweisimmen 19:59−2 min—
Sun 1 NovZweisimmen 19:59−2 min—
Sat 31 OctZweisimmen 19:59−1 min—
Fri 30 OctZweisimmen 20:00No data—
Thu 29 OctZweisimmen 20:000 min—
Wed 28 OctZweisimmen 19:59−1 min—
Tue 27 OctZweisimmen 20:00No data—
Mon 26 OctZweisimmen 20:000 min—
Sun 25 OctZweisimmen 19:59−1 min—
Sat 24 OctZweisimmen 19:59−1 min—
Fri 23 OctZweisimmen 20:02+2 min+2 min
Thu 22 OctZweisimmen 20:02+1 min+2 min
Wed 21 OctZweisimmen 19:59−1 min—
Tue 20 OctZweisimmen 19:59−1 min—
Mon 19 OctZweisimmen 20:000 min—
Sun 18 OctZweisimmen 19:59−1 min—
Sat 17 OctZweisimmen 20:000 min—
Fri 16 OctZweisimmen 19:59−1 min—
Thu 15 OctZweisimmen 20:19+19 min+20 min
Wed 14 OctZweisimmen 19:590 min—
Mon 12 OctZweisimmen 19:58−1 min—
Sun 11 OctZweisimmen 19:59−1 min—
Sat 10 OctZweisimmen 19:59−1 min—
Fri 9 OctZweisimmen 19:59−1 min—
Thu 8 OctZweisimmen 19:59−1 min—