S7 7673 Bern – Bolligen

View line S7

Bern 17:22 → Bolligen 17:33 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 5 stops RBS

✓ Today’s run finished

Today it reached Bolligen at 17:33 0 min

  1. Bern17:22
  2. Worblaufen17:26
  3. Papiermühle17:29
  4. Ittigen bei Bern17:30
  5. Bolligen17:33

Next service: tomorrow 17:22 from Bern · Thu 12 Nov

Next departure 17:22 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
72/75 runs under 3 min
RT coverage: 75 full · 0 partial · 1 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 Bolligen, 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 3 Sept Max en route +19 min · last fix heading to Dietikon +9 min
  • Sat 31 Oct Max en route +5 min · last fix heading to Dietikon +5 min
  • Mon 17 Aug Max en route +4 min · last fix heading to Dietikon +4 min

Distribution · 90 days

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

  • Early 11% · 8
  • On time 85% · 64
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • 100% T n=13
  • 100% W n=13
  • 91% T n=11
  • 100% F n=10
  • 89% S n=9
  • 100% S n=8

Stops and timetable

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

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