S7 7677 Bern – Bolligen

View line S7

Bern 17:52 → Bolligen 18:03 Mon, Tue, Wed, Thu, Fri 0 h 11 min · 5 stops RBS

✓ Today’s run finished

Today it reached Bolligen at 18:03 0 min

  1. Bern17:52
  2. Worblaufen17:56
  3. Papiermühle17:59
  4. Ittigen bei Bern18:00
  5. Bolligen18:03

Next service: tomorrow 17:52 from Bern · Fri 6 Nov

Next departure 17:52 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
96%
67/70 runs under 3 min
RT coverage: 70 full · 0 partial · 2 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: +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

  • Tue 18 Aug Max en route +6 min · last fix heading to Malpensa Aeroporto T2 +6 min
  • Tue 29 Sept Max en route +5 min · last fix heading to Bolligen +5 min
  • Wed 12 Aug Max en route +4 min · last fix heading to Dietikon Schöneggstrasse +4 min

Distribution · 90 days

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

  • Early 16% · 11
  • On time 80% · 56
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 82% T n=11
  • 92% W n=13
  • 100% T n=9
  • 100% F n=9
  • 100% S n=9
  • 100% S n=9

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