IC3 575 Basel SBB → Chur

View line IC3

Basel SBB 14:33 → Chur 16:52 Daily 2 h 19 min · 5 stops SBB CFF FFS

It has not run yet today

Last recorded run: Friday 20 November +4 min

Next service: today 14:33 from Basel SBB · Sat 21 Nov

Next departure 14:33 today · Basel SBB
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
99%
67/68 runs under 3 min
RT coverage: 68 full · 0 partial · 3 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
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

  • Fri 20 Nov Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 38% · 26
  • On time 60% · 41
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=11
  • 100% W n=10
  • 100% T n=7
  • 92% F n=12
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 68 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:33on time on time
15:26 / 15:38≈ on time ≈ on time
16:32 / 16:33≈ 1 min early ≈ on time
16:41 / 16:42≈ 1 min early ≈ on time
16:521 min early on time

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
Fri 20 NovChur 16:53+4 min+4 min
Thu 19 NovChur 16:520 min—
Wed 18 NovChur 16:49−2 min—
Tue 17 NovChur 16:52−1 min—
Mon 16 NovChur 16:49−1 min—
Sun 15 NovChur 16:49−2 min—
Sat 14 NovChur 16:52−1 min—
Fri 13 NovChur 16:52−2 min—
Thu 12 NovChur 16:49−1 min—
Wed 11 NovChur 16:52−1 min—
Tue 10 NovChur 16:49−1 min—
Mon 9 NovChur 16:49−1 min—
Sun 8 NovChur 16:52−1 min—
Sat 7 NovChur 16:530 min—
Fri 6 NovChur 16:52−1 min—
Thu 5 NovChur 16:52−1 min—
Wed 4 NovChur 16:530 min—
Tue 3 NovChur 16:52−1 min—
Mon 2 NovChur 16:52−1 min—
Sun 1 NovChur 16:530 min—
Sat 31 OctChur 16:51−1 min—
Fri 30 OctChur 16:52−1 min—
Thu 29 OctChur 16:53No data—
Wed 28 OctChur 16:530 min—
Tue 27 OctChur 16:530 min—
Mon 26 OctChur 16:52−2 min—
Sun 25 OctChur 16:520 min—
Sat 24 OctChur 16:530 min—
Fri 23 OctChur 16:53−1 min—
Thu 22 OctChur 16:52−1 min—