S7 7667 Bern – Bolligen

View line S7

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

✓ Today’s run finished

Today it reached Bolligen at 17:04 +1 min

  1. Bern16:52
  2. Worblaufen16:56
  3. Papiermühle16:59
  4. Ittigen bei Bern17:00
  5. Bolligen17:03

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

Next departure 16: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
97%
74/76 runs under 3 min
RT coverage: 76 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

  • Wed 7 Oct Max en route +5 min · last fix heading to Dietikon +5 min
  • Wed 23 Sept Max en route +3 min · last fix heading to Olten Hammer +3 min

Distribution · 90 days

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

  • Early 12% · 9
  • On time 86% · 65
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 76 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:52on time on time
16:56≈ on time ≈ +1 min
16:59≈ on time ≈ +1 min
17:00≈ on time ≈ +1 min
17:03on 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
Thu 19 NovBolligen 17:04+1 min+1 min
Wed 18 NovDietikon 21:29+1 min+2 min
Tue 17 NovDietikon 21:290 min—
Mon 16 NovDietikon 21:27−1 min—
Sun 15 NovDietikon 21:240 min—
Sat 14 NovDietikon 21:29+1 min+1 min
Fri 13 NovDietikon 21:29+1 min+1 min
Thu 12 NovDietikon 21:290 min—
Wed 11 NovDietikon 21:270 min+3 min
Tue 10 NovDietikon 21:28+1 min+2 min
Mon 9 NovDietikon 21:29+1 min+1 min
Sun 8 NovDietikon 21:240 min—
Sat 7 NovDietikon 21:27−1 min—
Fri 6 NovDietikon 21:240 min+1 min
Thu 5 NovDietikon 21:27−1 min+1 min
Wed 4 NovDietikon 21:29+1 min—
Tue 3 NovDietikon 21:290 min—
Mon 2 NovDietikon 21:280 min+1 min
Sun 1 NovDietikon 21:27−1 min+4 min
Sat 31 OctDietikon 21:270 min+1 min
Fri 30 OctDietikon 21:280 min+1 min
Thu 29 OctDietikon 21:27−1 min+1 min
Wed 28 OctDietikon 21:29+1 min—
Tue 27 OctDietikon 21:28−1 min—
Mon 26 OctDietikon 21:29+1 min—
Sun 25 OctDietikon 21:270 min—
Sat 24 OctDietikon 21:29+1 min+1 min
Fri 23 OctDietikon 21:29+1 min+8 min
Thu 22 OctDietikon 21:27−1 min+1 min
Wed 21 OctDietikon 21:27−1 min+1 min