S7 7664 Bolligen – Bern

View line S7

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

✓ Today’s run finished

Today it reached Bern at 16:47 0 min

  1. Bolligen16:36
  2. Ittigen bei Bern16:38
  3. Papiermühle16:40
  4. Worblaufen16:43
  5. Bern16:47

Next service: tomorrow 16:36 from Bolligen · Tue 10 Nov

Next departure 16:36 tomorrow · Bolligen
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
73/77 runs under 3 min
RT coverage: 77 full · 0 partial · 2 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −2 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bern, 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 +5 min · last fix heading to Luterbach-Attisholz +5 min
  • Fri 28 Aug Max en route +23 min · last fix heading to Biel Mett +4 min
  • Tue 25 Aug Max en route +3 min · last fix heading to Biel/Bienne +3 min
  • Wed 12 Aug Max en route +3 min · last fix heading to Wohlen AG +3 min

Distribution · 90 days

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

  • Early 45% · 35
  • On time 49% · 38
  • 3–10 min 5% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 80% T n=10
  • 92% W n=12
  • 100% T n=10
  • 92% F n=12
  • 100% S n=11
  • 100% S n=11

Stops and timetable

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

Last 90 days, 77 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:36on time +1 min
16:38≈ on time ≈ +1 min
16:40≈ on time ≈ +1 min
16:43≈ on time ≈ +1 min
16:471 min early +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
Mon 9 NovBern 16:480 min+1 min
Sun 8 NovWohlen AG 20:37−3 min+2 min
Sat 7 NovWohlen AG 20:340 min+2 min
Fri 6 NovWohlen AG 20:37+1 min+1 min
Thu 5 NovWohlen AG 20:38−1 min+3 min
Wed 4 NovWohlen AG 20:38−1 min+3 min
Tue 3 NovWohlen AG 20:37−2 min—
Mon 2 NovWohlen AG 20:38−2 min+2 min
Sun 1 NovWohlen AG 20:38−2 min+3 min
Sat 31 OctWohlen AG 20:37−2 min+1 min
Fri 30 OctWohlen AG 20:37−2 min+2 min
Thu 29 OctWohlen AG 20:360 min—
Wed 28 OctWohlen AG 20:38−1 min+2 min
Tue 27 OctWohlen AG 20:360 min—
Mon 26 OctWohlen AG 20:38−2 min—
Sun 25 OctWohlen AG 20:37−1 min+2 min
Sat 24 OctWohlen AG 20:37−2 min—
Fri 23 OctWohlen AG 20:41+2 min+4 min
Thu 22 OctWohlen AG 20:39−1 min+3 min
Wed 21 OctWohlen AG 20:38−1 min+1 min
Tue 20 OctWohlen AG 20:38−1 min+1 min
Mon 19 OctWohlen AG 20:37−2 min—
Sun 18 OctWohlen AG 20:36−2 min—
Sat 17 OctWohlen AG 20:37−2 min—
Fri 16 OctWohlen AG 20:37−2 min—
Thu 15 OctWohlen AG 20:37−2 min+2 min
Wed 14 OctWohlen AG 20:38−2 min+1 min
Tue 13 OctWohlen AG 20:37−2 min+1 min
Mon 12 OctWohlen AG 20:37−2 min—
Sun 11 OctWohlen AG 20:37−2 min—