S9 9203 Bern → Unterzollikofen

View line S9

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

S9 9203 Bern–Unterzollikofen: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 21:35 (GMT+1).

✓ Today’s run finished

Today it reached Unterzollikofen at 20:28 +2 min

  1. Bern20:16
  2. Bern Felsenau20:18
  3. Bern Tiefenau20:19
  4. Worblaufen20:22
  5. Steinibach20:23
  6. Unterzollikofen20:26

Next service: tomorrow 20:16 from Bern · Sun 22 Nov

Next departure 20: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
98%
53/54 runs under 3 min
RT coverage: 54 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: +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

  • Fri 18 Sept Max en route +17 min · last fix heading to Zürich HB +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 53
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • 100% S n=7
  • 100% S n=8

Stops and timetable

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

Last 90 days, 54 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
20:16on time on time
20:18≈ on time ≈ +2 min
20:19≈ on time ≈ +3 min
20:22≈ on time ≈ +2 min
20:23≈ on time ≈ +2 min
20: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
Sat 21 NovUnterzollikofen 20:28+2 min+3 min
Fri 20 NovUnterzollikofen 20:23+1 min—
Thu 19 NovUnterzollikofen 20:270 min—
Wed 18 NovUnterzollikofen 20:270 min+60 min
Tue 17 NovUnterzollikofen 20:28+1 min+5 min
Mon 16 NovUnterzollikofen 20:27+1 min—
Sun 15 NovUnterzollikofen 20:240 min—
Sat 14 NovUnterzollikofen 20:240 min—
Fri 13 NovUnterzollikofen 20:270 min—
Thu 12 NovUnterzollikofen 20:29+1 min+1 min
Wed 11 NovUnterzollikofen 20:27+1 min—
Tue 10 NovUnterzollikofen 20:28+2 min+5 min
Mon 9 NovUnterzollikofen 20:27+1 min+2 min
Sun 8 NovUnterzollikofen 20:28+1 min—
Sat 7 NovUnterzollikofen 20:270 min+11 min
Fri 6 NovUnterzollikofen 20:28+1 min+1 min
Thu 5 NovUnterzollikofen 20:270 min—
Wed 4 NovUnterzollikofen 20:28+1 min—
Tue 3 NovUnterzollikofen 20:270 min—
Mon 2 NovUnterzollikofen 20:29+1 min+1 min
Sun 1 NovUnterzollikofen 20:280 min+4 min
Sat 31 OctUnterzollikofen 20:27+1 min+6 min
Fri 30 OctUnterzollikofen 20:270 min—
Thu 29 OctUnterzollikofen 20:270 min—
Wed 28 OctUnterzollikofen 20:28+1 min+2 min
Tue 27 OctUnterzollikofen 20:28+1 min+5 min
Mon 26 OctUnterzollikofen 20:28+1 min+1 min
Sun 25 OctUnterzollikofen 20:270 min—
Sat 24 OctUnterzollikofen 20:28+1 min+1 min
Fri 23 OctUnterzollikofen 20:28+1 min+26 min