S9 9163 Bern – Unterzollikofen

View line S9

Bern 16:16 → Unterzollikofen 16:26 Daily 0 h 10 min · 6 stops RBS

✓ Today’s run finished

Today it reached Unterzollikofen at 16:27 +1 min

  1. Bern16:16
  2. Bern Felsenau16:18
  3. Bern Tiefenau16:19
  4. Worblaufen16:22
  5. Steinibach16:23
  6. Unterzollikofen16:26

Next service: tomorrow 16:16 from Bern · Wed 18 Nov

Next departure 16:16 tomorrow · 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 · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 44
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
16:16on time on time
16:18≈ on time ≈ on time
16:19≈ on time ≈ on time
16:22≈ on time ≈ +1 min
16:23≈ on time ≈ +1 min
16:26+1 min +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
Tue 17 NovUnterzollikofen 16:28+1 min—
Mon 16 NovUnterzollikofen 16:28+1 min—
Sun 15 NovUnterzollikofen 16:28+1 min—
Sat 14 NovUnterzollikofen 16:28+1 min+1 min
Fri 13 NovUnterzollikofen 16:28+1 min—
Thu 12 NovUnterzollikofen 16:28+1 min+1 min
Wed 11 NovUnterzollikofen 16:29+3 min+3 min
Tue 10 NovUnterzollikofen 16:29+2 min+2 min
Mon 9 NovUnterzollikofen 16:28+1 min—
Sun 8 NovUnterzollikofen 16:270 min—
Sat 7 NovUnterzollikofen 16:270 min—
Fri 6 NovUnterzollikofen 16:28+1 min—
Thu 5 NovUnterzollikofen 16:28+1 min+1 min
Wed 4 NovUnterzollikofen 16:28+1 min—
Tue 3 NovUnterzollikofen 16:270 min—
Mon 2 NovUnterzollikofen 16:28+2 min+2 min
Sun 1 NovUnterzollikofen 16:27+1 min—
Sat 31 OctUnterzollikofen 16:27+1 min—
Fri 30 OctUnterzollikofen 16:28+1 min—
Thu 29 OctUnterzollikofen 16:29+2 min+2 min
Wed 28 OctUnterzollikofen 16:28+1 min+1 min
Tue 27 OctUnterzollikofen 16:27+1 min—
Mon 26 OctUnterzollikofen 16:27+1 min—
Sun 25 OctUnterzollikofen 16:270 min—
Sat 24 OctUnterzollikofen 16:270 min—
Fri 23 OctUnterzollikofen 16:27+1 min—
Thu 22 OctUnterzollikofen 16:28+1 min+1 min
Wed 21 OctUnterzollikofen 16:28+1 min+1 min
Tue 20 OctUnterzollikofen 16:29+2 min+2 min
Mon 19 OctUnterzollikofen 16:28+1 min+1 min