ICE 373 Basel Bad Bf – Chur
Alerts for train 373
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line ICE.
✓ Today’s run finished
Today, last fix heading to Chur at 20:23 No data
- Basel Bad Bf17:41
- Basel SBB17:48
- Zürich HB19:00
- Sargans20:02
- Landquart20:11
- Chur20:22
Next service: tomorrow 17:41 from Basel Bad Bf · Mon 16 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
Worst days
- Fri 18 Sept Max en route +4 min · last fix heading to Chur +4 min
- Mon 28 Sept Max en route +5 min · last fix heading to Chur +4 min
- Thu 12 Nov Max en route +4 min · last fix heading to Langenthal +4 min
Distribution · 90 days
57 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 58% · 33
- On time 37% · 21
- 3–10 min 5% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 89% M n=9
- 100% T n=8
- 100% W n=8
- 88% T n=8
- 89% F n=9
- 100% S n=8
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 57 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 |
|---|---|---|---|
| 17:41 | on time | +2 min | |
| 17:48 / 18:04 | ≈ on time | ≈ +2 min | |
| 19:00 / 19:07 | ≈ 1 min early | ≈ +2 min | |
| 20:02 / 20:03 | ≈ 2 min early | ≈ +2 min | |
| 20:11 / 20:12 | ≈ 2 min early | ≈ +2 min | |
| 20:22 | 2 min early | +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 |
|---|---|---|---|
| Sun 15 Nov | Chur 20:23 | No data | — |
| Sat 14 Nov | Langenthal 21:39 | −1 min | — |
| Fri 13 Nov | Langenthal 21:39 | +2 min | +2 min |
| Thu 12 Nov | Langenthal 21:44 | +4 min | +4 min |
| Wed 11 Nov | Langenthal 21:43 | +1 min | +3 min |
| Tue 10 Nov | Langenthal 21:39 | −3 min | — |
| Mon 9 Nov | Langenthal 21:39 | −3 min | — |
| Sun 8 Nov | Langenthal 21:39 | 0 min | — |
| Sat 7 Nov | Langenthal 21:39 | −3 min | — |
| Fri 6 Nov | Langenthal 21:39 | −3 min | +1 min |
| Thu 5 Nov | Langenthal 21:39 | −1 min | — |
| Wed 4 Nov | Langenthal 21:44 | +2 min | +3 min |
| Tue 3 Nov | Langenthal 21:39 | +1 min | — |
| Mon 2 Nov | Langenthal 21:39 | +2 min | +2 min |
| Sun 1 Nov | Langenthal 21:39 | −1 min | — |
| Sat 31 Oct | Langenthal 21:39 | −3 min | — |
| Fri 30 Oct | Langenthal 21:40 | −1 min | +1 min |
| Thu 29 Oct | Langenthal 21:39 | +1 min | +1 min |
| Wed 28 Oct | Langenthal 21:39 | −3 min | — |
| Tue 27 Oct | Langenthal 21:40 | −2 min | — |
| Mon 26 Oct | Langenthal 21:40 | −2 min | +2 min |
| Sun 25 Oct | Langenthal 21:39 | −3 min | — |
| Sat 24 Oct | Langenthal 21:38 | −3 min | — |
| Fri 23 Oct | Langenthal 21:39 | −3 min | — |
| Thu 22 Oct | Langenthal 21:41 | −2 min | +3 min |
| Wed 21 Oct | Langenthal 21:40 | −1 min | +1 min |
| Tue 20 Oct | Langenthal 21:44 | +1 min | +4 min |
| Mon 19 Oct | Langenthal 21:42 | 0 min | — |
| Sun 18 Oct | Langenthal 21:41 | −2 min | — |
| Sat 17 Oct | Langenthal 21:39 | −3 min | — |