S7 7221 Bern – Bolligen

View line S7

Bern 22:00 → Bolligen 22:11 Daily 0 h 11 min · 5 stops RBS

✓ Today’s run finished

Today it reached Bolligen at 22:12 +1 min

  1. Bern22:00
  2. Worblaufen22:04
  3. Papiermühle22:07
  4. Ittigen bei Bern22:08
  5. Bolligen22:11

Next service: tomorrow 22:00 from Bern · Sat 21 Nov

Next departure 22:00 tomorrow · Bern
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
50/51 runs under 3 min
RT coverage: 51 full · 0 partial · 0 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

  • Sat 7 Nov Max en route +3 min · last fix heading to Bolligen +3 min

Distribution · 90 days

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

  • Early 16% · 8
  • On time 82% · 42
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 51 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
22:00+1 min +1 min
22:04≈ on time ≈ +1 min
22:07≈ on time ≈ +1 min
22:08≈ on time ≈ +1 min
22:11on 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 20 NovBolligen 22:12+1 min—
Thu 19 NovBolligen 22:090 min—
Wed 18 NovBolligen 22:090 min—
Tue 17 NovBolligen 22:12−1 min—
Mon 16 NovBolligen 22:090 min—
Sun 15 NovSonceboz-Sombeval 12:19−1 min—
Sat 14 NovBolligen 22:130 min—
Fri 13 NovBolligen 22:13+1 min—
Thu 12 NovBolligen 22:130 min—
Wed 11 NovBolligen 22:090 min—
Tue 10 NovBolligen 22:12+1 min—
Mon 9 NovBolligen 22:11−1 min—
Sun 8 NovSonceboz-Sombeval 12:19−1 min—
Sat 7 NovBolligen 22:14+3 min+3 min
Fri 6 NovBolligen 22:130 min—
Thu 5 NovBolligen 22:090 min—
Wed 4 NovBolligen 22:120 min—
Tue 3 NovBolligen 22:120 min—
Mon 2 NovBolligen 22:12−1 min—
Sun 1 NovSonceboz-Sombeval 12:19−1 min—
Sat 31 OctBolligen 22:11−1 min—
Fri 30 OctBolligen 22:11−1 min—
Thu 29 OctBolligen 22:120 min—
Wed 28 OctBolligen 22:120 min—
Tue 27 OctBolligen 22:12−1 min—
Mon 26 OctBolligen 22:11−1 min—
Sun 25 OctSonceboz-Sombeval 12:190 min—
Sat 24 OctBolligen 22:110 min—
Fri 23 OctBolligen 22:11−1 min—
Thu 22 OctBolligen 22:11−1 min—