S9 9145 Bern – Unterzollikofen

View line S9

Bern 14:31 → Unterzollikofen 14:41 Daily 0 h 10 min · 6 stops RBS

✓ Today’s run finished

Today it reached Unterzollikofen at 14:41 0 min

  1. Bern14:31
  2. Bern Felsenau14:33
  3. Bern Tiefenau14:34
  4. Worblaufen14:37
  5. Steinibach14:38
  6. Unterzollikofen14:41

Next service: tomorrow 14:31 from Bern · Thu 19 Nov

Next departure 14:31 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%
46/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

Distribution · 90 days

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

  • Early 17% · 8
  • On time 83% · 38
  • 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=7
  • 100% T n=7
  • 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, 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
14:31on time on time
14:33≈ on time ≈ on time
14:34≈ on time ≈ on time
14:37≈ on time ≈ +1 min
14:38≈ on time ≈ +1 min
14:41on 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 14:420 min—
Tue 17 NovMeiringen 17:390 min+1 min
Mon 16 NovMeiringen 17:39−1 min+1 min
Sun 15 NovUnterzollikofen 14:43+1 min—
Sat 14 NovUnterzollikofen 14:43+1 min—
Fri 13 NovMeiringen 17:39−3 min+1 min
Thu 12 NovMeiringen 17:390 min—
Wed 11 NovMeiringen 17:390 min—
Tue 10 NovMeiringen 17:390 min+1 min
Mon 9 NovMeiringen 17:390 min—
Sun 8 NovUnterzollikofen 14:420 min—
Sat 7 NovUnterzollikofen 14:420 min—
Fri 6 NovMeiringen 17:390 min+1 min
Thu 5 NovMeiringen 17:39−1 min—
Wed 4 NovMeiringen 17:42+1 min+1 min
Tue 3 NovMeiringen 17:42+1 min+1 min
Mon 2 NovMeiringen 17:42+1 min+1 min
Sun 1 NovUnterzollikofen 14:43+1 min+1 min
Sat 31 OctUnterzollikofen 14:43+1 min—
Fri 30 OctMeiringen 17:43+2 min+3 min
Thu 29 OctMeiringen 17:43+2 min+4 min
Wed 28 OctMeiringen 17:420 min—
Tue 27 OctMeiringen 17:40−1 min—
Mon 26 OctMeiringen 17:40−1 min—
Sun 25 OctUnterzollikofen 14:420 min—
Sat 24 OctUnterzollikofen 14:42+1 min—
Fri 23 OctMeiringen 17:40−1 min+1 min
Thu 22 OctMeiringen 17:39−1 min—
Wed 21 OctMeiringen 17:41+1 min+2 min
Tue 20 OctMeiringen 17:39−2 min—