IR35 2383 Bern – Chur
Alerts for train 2383
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line IR35.
It does not run today
Last recorded run: Saturday 7 November +2 min
Next service: tomorrow 18:38 from Bern · Mon 9 Nov
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
Distribution · 90 days
39 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 5% · 2
- On time 95% · 37
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=6
- 100% W n=6
- 100% T n=6
- 100% F n=5
- 100% S n=7
- 100% S n=4
Stops and timetable
Timetable of the latest run from the operator’s GTFS (20 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 18:38 | on time | on time | |
| 18:52 / 18:53 | ≈ on time | ≈ on time | |
| 19:04 / 19:05 | ≈ on time | ≈ +1 min | |
| 19:10 / 19:12 | ≈ on time | ≈ +1 min | |
| 19:24 / 19:30 | ≈ on time | ≈ +1 min | |
| 20:00 | ≈ on time | ≈ +1 min | |
| 20:06 / 20:12 | ≈ on time | ≈ +1 min | |
| 20:21 | ≈ on time | ≈ +1 min | |
| 20:31 | ≈ on time | ≈ +1 min | |
| 20:39 / 20:41 | ≈ on time | ≈ +1 min | |
| 20:48 | ≈ on time | ≈ +1 min | |
| 20:58 / 21:00 | ≈ on time | ≈ +1 min | |
| 21:10 / 21:11 | ≈ on time | ≈ +1 min | |
| 21:15 | ≈ on time | ≈ +1 min | |
| 21:18 / 21:19 | ≈ on time | ≈ +1 min | |
| 21:25 / 21:27 | ≈ on time | ≈ +1 min | |
| 21:31 | ≈ on time | ≈ +1 min | |
| 21:34 | ≈ on time | ≈ +1 min | |
| 21:39 | ≈ on time | ≈ +1 min | |
| 21:48 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 7 Nov | Chur 21:49 | +2 min | +2 min |
| Fri 6 Nov | Chur 21:49 | +1 min | +1 min |
| Thu 5 Nov | Chur 21:49 | +1 min | — |
| Wed 4 Nov | Chur 21:48 | −1 min | — |
| Tue 3 Nov | Chur 21:49 | 0 min | — |
| Mon 2 Nov | Chur 21:49 | 0 min | — |
| Sun 1 Nov | Chur 21:49 | 0 min | — |
| Sat 31 Oct | Chur 21:50 | +2 min | +2 min |
| Fri 30 Oct | Chur 21:48 | −1 min | — |
| Thu 29 Oct | Chur 21:48 | −1 min | +4 min |
| Wed 28 Oct | Chur 21:49 | 0 min | — |
| Tue 27 Oct | Chur 21:49 | 0 min | — |
| Mon 26 Oct | Chur 21:48 | −1 min | — |
| Sun 25 Oct | Chur 21:49 | +1 min | +10 min |
| Sat 24 Oct | Chur 21:51 | +2 min | +2 min |
| Fri 23 Oct | Chur 21:50 | +1 min | +1 min |
| Thu 22 Oct | Chur 21:48 | −1 min | — |
| Wed 21 Oct | Chur 21:49 | +1 min | — |
| Tue 20 Oct | Chur 21:49 | −1 min | — |
| Mon 19 Oct | Chur 21:48 | 0 min | — |
| Sun 18 Oct | Chur 21:50 | 0 min | — |
| Sat 17 Oct | Chur 21:50 | +1 min | — |
| Fri 16 Oct | Chur 21:49 | 0 min | — |
| Thu 15 Oct | Chur 21:48 | −1 min | — |
| Wed 14 Oct | Chur 21:50 | +1 min | — |
| Tue 13 Oct | Chur 21:49 | 0 min | — |
| Mon 12 Oct | Chur 21:47 | −1 min | — |
| Fri 9 Oct | Chur 21:50 | 0 min | — |
| Thu 8 Oct | Chur 21:51 | +1 min | +1 min |
| Wed 7 Oct | Chur 21:50 | +1 min | +1 min |