S7 7665 Bern – Bolligen

View line S7

Bern 16:37 → Bolligen 16:48 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 5 stops RBS

✓ Today’s run finished

Today it reached Bolligen at 16:49 +1 min

  1. Bern16:37
  2. Worblaufen16:41
  3. Papiermühle16:44
  4. Ittigen bei Bern16:45
  5. Bolligen16:48

Next service: tomorrow 16:37 from Bern · Fri 20 Nov

Next departure 16:37 tomorrow · Bern
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
70/70 runs under 3 min
RT coverage: 70 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 Bolligen, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 6% · 4
  • On time 94% · 66
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 100% T n=10
  • 100% W n=11
  • 100% T n=9
  • 100% F n=12
  • 100% S n=10
  • 100% S n=8

Stops and timetable

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

Last 90 days, 70 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
16:37on time on time
16:41≈ on time ≈ on time
16:44≈ on time ≈ +1 min
16:45≈ on time ≈ +1 min
16:48+1 min +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
Thu 19 NovBolligen 16:50+1 min+1 min
Wed 18 NovDietikon 20:58+1 min+3 min
Tue 17 NovDietikon 20:590 min+1 min
Mon 16 NovDietikon 20:540 min+2 min
Sun 15 NovDietikon 20:570 min—
Sat 14 NovDietikon 20:58+1 min+1 min
Fri 13 NovDietikon 20:58+1 min+1 min
Thu 12 NovDietikon 20:59+1 min+1 min
Wed 11 NovDietikon 20:57−1 min+1 min
Tue 10 NovDietikon 20:58+1 min+1 min
Mon 9 NovDietikon 20:58+1 min+3 min
Sun 8 NovDietikon 20:59+1 min—
Sat 7 NovDietikon 20:57−1 min+1 min
Fri 6 NovDietikon 20:54+1 min—
Thu 5 NovDietikon 20:59+1 min—
Wed 4 NovDietikon 20:580 min+2 min
Tue 3 NovDietikon 20:59+1 min—
Mon 2 NovDietikon 20:59+1 min+2 min
Sun 1 NovDietikon 20:57−1 min—
Sat 31 OctDietikon 20:59+1 min—
Fri 30 OctDietikon 20:570 min+1 min
Thu 29 OctDietikon 20:59+1 min+2 min
Wed 28 OctDietikon 20:580 min+1 min
Tue 27 OctDietikon 20:59+1 min+2 min
Mon 26 OctDietikon 20:59+1 min+2 min
Sun 25 OctDietikon 20:59+1 min+2 min
Sat 24 OctDietikon 20:59+2 min+2 min
Fri 23 OctDietikon 20:57−1 min+1 min
Thu 22 OctDietikon 20:590 min—
Wed 21 OctDietikon 20:59+1 min+1 min