S9 9107 Bern – Unterzollikofen

View line S9

Bern 10:46 → Unterzollikofen 10:56 Daily 0 h 10 min · 6 stops RBS

It has not run yet today

Last recorded run: Wednesday 18 November +1 min

Next service: today 10:46 from Bern · Thu 19 Nov

Next departure 10:46 today · Bern
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
98%
45/46 runs under 3 min
RT coverage: 46 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 Unterzollikofen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +6 min · last fix heading to Unterzollikofen +6 min

Distribution · 90 days

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

  • Early 22% · 10
  • On time 76% · 35
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
10:46+1 min +2 min
10:48≈ +1 min ≈ +1 min
10:49≈ +1 min ≈ +1 min
10:52≈ on time ≈ +1 min
10:53≈ on time ≈ +1 min
10:56on 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
Wed 18 NovUnterzollikofen 10:58+1 min—
Tue 17 NovUnterzollikofen 10:58+1 min+1 min
Mon 16 NovUnterzollikofen 10:570 min—
Sun 15 NovUnterzollikofen 10:58+1 min—
Sat 14 NovUnterzollikofen 10:57+1 min+1 min
Fri 13 NovUnterzollikofen 10:58+1 min—
Thu 12 NovUnterzollikofen 10:58+1 min—
Wed 11 NovUnterzollikofen 10:570 min—
Tue 10 NovUnterzollikofen 10:540 min+2 min
Mon 9 NovUnterzollikofen 10:58+1 min+1 min
Sun 8 NovZermatt 19:390 min—
Sat 7 NovZermatt 19:39+1 min—
Fri 6 NovZermatt 19:390 min—
Thu 5 NovZermatt 19:390 min+2 min
Wed 4 NovZermatt 19:39−1 min+2 min
Tue 3 NovZermatt 19:390 min+2 min
Mon 2 NovZermatt 19:39−1 min+2 min
Sun 1 NovZermatt 19:390 min—
Sat 31 OctZermatt 19:39−1 min—
Fri 30 OctZermatt 19:390 min—
Thu 29 OctZermatt 19:410 min—
Wed 28 OctZermatt 19:39−1 min—
Tue 27 OctZermatt 19:39−1 min—
Mon 26 OctZermatt 19:40−2 min—
Sun 25 OctZermatt 19:410 min—
Sat 24 OctZermatt 19:40−1 min+4 min
Fri 23 OctZermatt 19:42+1 min+1 min
Thu 22 OctZermatt 19:40−1 min—
Wed 21 OctZermatt 19:39−2 min+2 min
Tue 20 OctZermatt 19:40−2 min+1 min