IR35 2359 Bern – Chur

View line IR35

Bern 06:38 → Chur 09:48 Mon, Tue, Wed, Thu, Fri 3 h 10 min · 20 stops SOB

Running now · updated 07:07

Position estimated from the timetable

Between Herzogenbuchsee and Langenthal 0 min

Estimated arrival at Chur 09:48 · 90 km/h

  1. Bern06:38
  2. Herzogenbuchsee07:04
  3. Langenthal07:10
  4. Zürich HB08:06
  5. Siebnen-Wangen08:48
  6. Walenstadt09:15
  7. Chur09:48

Today it is running worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 46 full · 1 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: 0 min

Last 30 days

Arrival delay at Chur, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 8 Nov Max en route +22 min · last fix heading to Chur +13 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 21% · 10
  • On time 74% · 35
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (20 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 10Today
06:38on time on timePassed
06:52 / 06:53≈ on time ≈ on timePassed
07:04 / 07:05≈ on time ≈ on timePassed
07:10 / 07:12≈ on time ≈ on timeNext
07:24 / 07:30≈ on time ≈ +1 min
08:00≈ on time ≈ +1 min
08:06 / 08:12≈ on time ≈ +1 min
08:21≈ on time ≈ +1 min
08:31≈ on time ≈ +1 min
08:39 / 08:41≈ on time ≈ +1 min
08:48≈ on time ≈ +1 min
08:58 / 09:00≈ on time ≈ +1 min
09:10 / 09:11≈ on time ≈ +1 min
09:15≈ on time ≈ +1 min
09:18 / 09:19≈ on time ≈ +1 min
09:25 / 09:26≈ on time ≈ +1 min
09:30≈ on time ≈ +1 min
09:33≈ on time ≈ +1 min
09:38≈ on time ≈ +1 min
09: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
Tue 17 NovHerzogenbuchsee 07:04Partial coverage0 min—
Mon 16 NovChur 09:480 min—
Sun 15 NovChur 09:490 min—
Sat 14 NovChur 09:49+1 min+1 min
Fri 13 NovChur 09:490 min—
Thu 12 NovChur 09:49−1 min—
Wed 11 NovChur 09:490 min—
Tue 10 NovChur 09:48−1 min—
Mon 9 NovChur 09:48−1 min—
Sun 8 NovChur 10:03+13 min+22 min
Sat 7 NovChur 09:490 min—
Fri 6 NovChur 09:490 min—
Thu 5 NovChur 09:49+2 min+2 min
Wed 4 NovChur 09:48−1 min—
Tue 3 NovChur 09:490 min—
Mon 2 NovChur 09:48−1 min—
Sun 1 NovChur 09:490 min—
Sat 31 OctChur 09:48−1 min—
Fri 30 OctChur 09:490 min—
Thu 29 OctChur 09:490 min—
Wed 28 OctChur 09:490 min—
Tue 27 OctChur 09:48−1 min—
Mon 26 OctBern 11:01−1 min—
Sun 25 OctChur 09:490 min—
Sat 24 OctChur 09:490 min—
Fri 23 OctChur 09:48−1 min—
Thu 22 OctChur 09:49−1 min—
Wed 21 OctChur 09:48−1 min—
Tue 20 OctChur 09:48−2 min—
Mon 19 OctChur 09:490 min—