IR65 3352 Biel/Bienne → Bern

View line IR65

Biel/Bienne 14:22 → Bern 14:48 Daily 0 h 26 min · 3 stops BLS

IR65 3352 Biel/Bienne–Bern: final delay under 3 min on 22 of its 24 runs with data in the last 30 days (92%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 16:50 (GMT+1).

✓ Today’s run finished

Today it reached Bern at 14:49 +1 min

  1. Biel/Bienne14:22
  2. Lyss14:30
  3. Bern14:48

Next service: tomorrow 14:22 from Biel/Bienne · Sun 22 Nov

Next departure 14:22 tomorrow · Biel/Bienne
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
92%
46/50 runs under 3 min
RT coverage: 50 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Wed 18 Nov Max en route +9 min · last fix heading to Bern +9 min
  • Fri 28 Aug Max en route +9 min · last fix heading to Montreux-Les Planches +7 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Bern +4 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Bern +4 min

Distribution · 90 days

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

  • Early 14% · 7
  • On time 78% · 39
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 86% T n=7
  • 88% W n=8
  • 83% T n=6
  • 88% F n=8
  • 100% S n=10
  • 100% S n=8

Stops and timetable

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

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