S7 7605 Bern – Bolligen

View line S7

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

✓ Today’s run finished

Today it reached Bolligen at 06:49 +1 min

  1. Bern06:37
  2. Worblaufen06:41
  3. Papiermühle06:44
  4. Ittigen bei Bern06:45
  5. Bolligen06:48

Next service: Monday 06:37 from Bern · Mon 9 Nov

Next departure 06:37 Monday · 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%
44/44 runs under 3 min
RT coverage: 44 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

Distribution · 90 days

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

  • Early 18% · 8
  • On time 82% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=7
  • 100% T n=6
  • 100% F n=6
  • 100% S n=4
  • 100% S n=8

Stops and timetable

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

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