IR65 3384 Biel/Bienne – Bern

View line IR65

Biel/Bienne 22:22 → Bern 22:48 Daily 0 h 26 min · 3 stops SBB CFF FFS

It has not run yet today

Last recorded run: Wednesday 4 November −1 min

Next service: today 22:22 from Biel/Bienne · Thu 5 Nov

Next departure 22:22 today · Biel/Bienne
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 1 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: +2 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

Worst days

  • Mon 12 Oct Max en route +4 min · last fix heading to Bern +4 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Bern +3 min

Distribution · 90 days

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

  • Early 10% · 4
  • On time 85% · 33
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 39 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
22:22on time +1 min
22:30 / 22:31≈ on time ≈ +1 min
22:48on 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 4 NovBern 22:48−1 min—
Tue 3 NovBern 22:48−1 min—
Mon 2 NovBern 22:490 min—
Sun 1 NovBern 22:49−1 min—
Sat 31 OctBern 22:490 min—
Fri 30 OctBern 22:49No data—
Thu 29 OctBern 22:48−1 min—
Wed 28 OctBern 22:48−1 min—
Tue 27 OctBern 22:48−1 min—
Mon 26 OctBern 22:490 min—
Sun 25 OctBern 22:47−2 min—
Sat 24 OctBern 22:51+2 min+2 min
Fri 23 OctBern 22:490 min—
Thu 22 OctBern 22:490 min—
Wed 21 OctBern 22:49+1 min—
Tue 20 OctBern 22:48−1 min—
Mon 19 OctBern 22:480 min—
Sun 18 OctBern 22:48−2 min—
Sat 17 OctBern 22:50+1 min+1 min
Fri 16 OctBern 22:490 min—
Thu 15 OctBern 22:48−1 min—
Wed 14 OctBern 22:53+3 min+3 min
Tue 13 OctBern 22:490 min—
Mon 12 OctBern 22:53+4 min+4 min
Sun 11 OctBern 22:50+1 min—
Sat 10 OctBern 22:500 min—
Fri 9 OctBern 22:47−2 min—
Thu 8 OctBern 22:500 min—
Wed 7 OctBern 22:49−1 min—
Tue 6 OctBern 22:49+1 min—