IR17 2819 Bern → Olten
Alerts for train 2819
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line IR17.
IR17 2819 Bern–Olten: final delay under 3 min on 20 of its 22 runs with data in the last 30 days (91%). Median final delay: +1 min. TrainsRadar data as of 22 Nov 2026, 12:13 (GMT+1).
An alert on this phone or computer when the 2819 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today it reached Olten at 11:55 +1 min
- Bern11:07
- Burgdorf11:20
- Wynigen11:26
- Herzogenbuchsee11:33
- Langenthal11:40
- Olten11:54
Next service: tomorrow 11:07 from Bern · Mon 23 Nov
Last 30 days
Arrival delay at Olten, 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 15 Nov Max en route +7 min · last fix heading to Metz Ville +7 min
- Sun 25 Oct Max en route +5 min · last fix heading to Olten +5 min
- Sun 18 Oct Max en route +3 min · last fix heading to Olten +3 min
Distribution · 90 days
39 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 92% · 36
- 3–10 min 8% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- 100% T n=7
- 100% W n=7
- 100% T n=1
- 100% F n=7
- 100% S n=7
- 67% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 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 |
|---|---|---|---|
| 11:07 | on time | on time | |
| 11:20 / 11:21 | ≈ on time | ≈ +1 min | |
| 11:26 / 11:27 | ≈ on time | ≈ +1 min | |
| 11:33 / 11:34 | ≈ on time | ≈ +1 min | |
| 11:40 / 11:41 | ≈ on time | ≈ +2 min | |
| 11:54 | +1 min | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 22 Nov | Olten 11:57 | +1 min | +1 min |
| Sat 21 Nov | Olten 11:54 | +1 min | +1 min |
| Fri 20 Nov | Olten 11:54 | 0 min | — |
| Thu 19 Nov | Olten 11:54 | No data | — |
| Wed 18 Nov | Olten 11:54 | +1 min | — |
| Tue 17 Nov | Olten 11:55 | 0 min | — |
| Mon 16 Nov | Olten 11:54 | No data | — |
| Sun 15 Nov | Metz Ville 16:39 | +7 min | +7 min |
| Sat 14 Nov | Olten 11:54 | +1 min | — |
| Fri 13 Nov | Olten 11:54 | 0 min | — |
| Thu 12 Nov | Olten 11:54 | No data | — |
| Wed 11 Nov | Olten 11:54 | 0 min | — |
| Tue 10 Nov | Olten 11:54 | +1 min | — |
| Mon 9 Nov | Olten 11:54 | No data | — |
| Sun 8 Nov | Metz Ville 16:42 | +2 min | +2 min |
| Sat 7 Nov | Olten 11:54 | 0 min | — |
| Fri 6 Nov | Olten 11:54 | 0 min | — |
| Thu 5 Nov | Olten 11:54 | No data | — |
| Wed 4 Nov | Olten 11:54 | 0 min | — |
| Tue 3 Nov | Olten 11:54 | +1 min | — |
| Mon 2 Nov | Olten 11:54 | No data | — |
| Sun 1 Nov | Olten 11:55 | +1 min | — |
| Sat 31 Oct | Olten 11:55 | +1 min | — |
| Fri 30 Oct | Olten 11:55 | 0 min | — |
| Thu 29 Oct | Olten 11:55 | No data | — |
| Wed 28 Oct | Olten 11:56 | +1 min | +1 min |
| Tue 27 Oct | Olten 11:56 | +1 min | — |
| Mon 26 Oct | Olten 11:56 | No data | — |
| Sun 25 Oct | Olten 11:59 | +5 min | +5 min |
| Sat 24 Oct | Olten 11:56 | +1 min | — |