S9 9174 Unterzollikofen – Bern

View line S9

Unterzollikofen 17:32 → Bern 17:43 Daily 0 h 11 min · 6 stops RBS

✓ Today’s run finished

Today it reached Bern at 17:44 +1 min

  1. Unterzollikofen17:32
  2. Steinibach17:34
  3. Worblaufen17:36
  4. Bern Tiefenau17:38
  5. Bern Felsenau17:39
  6. Bern17:43

Next service: tomorrow 17:32 from Unterzollikofen · Sat 21 Nov

Next departure 17:32 tomorrow · Unterzollikofen
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%
47/47 runs under 3 min
RT coverage: 47 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bern, 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

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

  • Early 40% · 19
  • On time 60% · 28
  • 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=7
  • 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, 47 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:32on time on time
17:34≈ on time ≈ on time
17:36≈ on time ≈ on time
17:38≈ on time ≈ on time
17:39≈ 1 min early ≈ on time
17:431 min early on time

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 NovBern 17:44+1 min—
Thu 19 NovBern 17:43−1 min—
Wed 18 NovBern 17:43−1 min—
Tue 17 NovBern 17:440 min—
Mon 16 NovBern 17:440 min—
Sun 15 NovBern 17:440 min—
Sat 14 NovBern 17:440 min—
Fri 13 NovBern 17:440 min—
Thu 12 NovBern 17:43−1 min—
Wed 11 NovBern 17:43−1 min—
Tue 10 NovBern 17:43−1 min—
Mon 9 NovBern 17:440 min—
Sun 8 NovBern 17:43−2 min—
Sat 7 NovBern 17:42−1 min—
Fri 6 NovBern 17:43−1 min—
Thu 5 NovBern 17:440 min—
Wed 4 NovBern 17:43−1 min—
Tue 3 NovBern 17:43−1 min—
Mon 2 NovBern 17:440 min—
Sun 1 NovBern 17:43−1 min—
Sat 31 OctBern 17:42−1 min—
Fri 30 OctBern 17:43−1 min—
Thu 29 OctBern 17:430 min—
Wed 28 OctBern 17:440 min—
Tue 27 OctBern 17:43−1 min—
Mon 26 OctBern 17:43−1 min—
Sun 25 OctBern 17:42−1 min—
Sat 24 OctBern 17:43−1 min—
Fri 23 OctBern 17:43−1 min—
Thu 22 OctBern 17:440 min—