S7 7654 Bolligen – Bern

View line S7

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

✓ Today’s run finished

Today, last fix heading to Bern at 13:48 No data

  1. Bolligen13:36
  2. Ittigen bei Bern13:38
  3. Papiermühle13:40
  4. Worblaufen13:43
  5. Bern13:47

Next service: tomorrow 13:36 from Bolligen · Fri 6 Nov

Next departure 13:36 tomorrow · Bolligen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 40% · 17
  • On time 60% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 43 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
13:36on time on time
13:38≈ on time ≈ on time
13:40≈ on time ≈ +1 min
13:43≈ on time ≈ +1 min
13:47on 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 NovBern 13:48No data—
Wed 4 NovWohlen AG 18:09+3 min+3 min
Tue 3 NovWohlen AG 18:09+2 min+2 min
Mon 2 NovWohlen AG 18:12+2 min+2 min
Sun 1 NovWohlen AG 18:08−1 min—
Sat 31 OctWohlen AG 18:12+3 min+3 min
Fri 30 OctWohlen AG 18:10+1 min+1 min
Thu 29 OctWohlen AG 18:11+2 min+2 min
Wed 28 OctWohlen AG 18:11+2 min+5 min
Tue 27 OctWohlen AG 18:090 min+2 min
Mon 26 OctWohlen AG 18:09−1 min+5 min
Sun 25 OctWohlen AG 18:070 min—
Sat 24 OctWohlen AG 18:09+2 min+2 min
Fri 23 OctWohlen AG 18:08−1 min+6 min
Thu 22 OctWohlen AG 18:08−1 min—
Wed 21 OctWohlen AG 18:11+2 min+5 min
Tue 20 OctWohlen AG 18:11+2 min+2 min
Mon 19 OctWohlen AG 18:08−1 min+1 min
Sun 18 OctWohlen AG 18:08−1 min+3 min
Sat 17 OctWohlen AG 18:07−2 min—
Fri 16 OctWohlen AG 18:12+2 min+3 min
Thu 15 OctWohlen AG 18:10+1 min+1 min
Wed 14 OctWohlen AG 18:10+2 min+2 min
Tue 13 OctWohlen AG 18:11+2 min+2 min
Mon 12 OctWohlen AG 18:10+2 min+2 min
Sun 11 OctWohlen AG 18:08−1 min+1 min
Sat 10 OctWohlen AG 18:07−3 min—
Fri 9 OctWohlen AG 18:09−1 min+1 min
Thu 8 OctWohlen AG 18:08−1 min—
Wed 7 OctWohlen AG 18:08+1 min—