S9 9171 Bern – Unterzollikofen

View line S9

Bern 17:01 → Unterzollikofen 17:11 Daily 0 h 10 min · 6 stops RBS

✓ Today’s run finished

Today it reached Unterzollikofen at 17:13 +2 min

  1. Bern17:01
  2. Bern Felsenau17:03
  3. Bern Tiefenau17:04
  4. Worblaufen17:07
  5. Steinibach17:08
  6. Unterzollikofen17:11

Next service: tomorrow 17:01 from Bern · Thu 12 Nov

Next departure 17:01 tomorrow · Bern
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
36/38 runs under 3 min
RT coverage: 38 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

Worst days

  • Wed 14 Oct Max en route +4 min · last fix heading to Unterzollikofen +4 min
  • Tue 20 Oct Max en route +3 min · last fix heading to Unterzollikofen +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 36
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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