IC3 583 Basel SBB – Chur

View line IC3

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

It has not run yet today

Last recorded run: Thursday 5 November −2 min

Next service: today 18:33 from Basel SBB · Fri 6 Nov

Next departure 18:33 today · Basel SBB
On-time · 30 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
97%
59/61 runs under 3 min
RT coverage: 61 full · 0 partial · 5 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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 18 Oct Max en route +5 min · last fix heading to Chur +4 min
  • Thu 29 Oct Max en route +3 min · last fix heading to Chur +3 min

Distribution · 90 days

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

  • Early 31% · 19
  • On time 66% · 40
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=9
  • 100% W n=9
  • 89% T n=9
  • 100% F n=9
  • 100% S n=8
  • 88% S n=8

Stops and timetable

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

Last 90 days, 61 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
18:33on time on time
19:26 / 19:38≈ on time ≈ +1 min
20:32 / 20:33≈ 1 min early ≈ +1 min
20:41 / 20:42≈ 1 min early ≈ +1 min
20:521 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

DateLast stopFinalMax
Thu 5 NovChur 20:49−2 min—
Wed 4 NovChur 20:49−2 min—
Tue 3 NovChur 20:52−1 min—
Mon 2 NovChur 20:52−2 min—
Sun 1 NovChur 20:530 min—
Sat 31 OctChur 20:55+2 min+2 min
Fri 30 OctChur 20:520 min—
Thu 29 OctChur 20:53+3 min+3 min
Wed 28 OctChur 20:52−1 min—
Tue 27 OctChur 20:540 min—
Mon 26 OctChur 20:51−2 min—
Sun 25 OctChur 20:51−1 min—
Sat 24 OctChur 20:53+1 min—
Fri 23 OctChur 20:54+1 min—
Thu 22 OctChur 20:530 min—
Wed 21 OctChur 20:530 min—
Tue 20 OctChur 20:530 min—
Mon 19 OctChur 20:52−1 min—
Sun 18 OctChur 20:57+4 min+5 min
Sat 17 OctChur 20:52−1 min—
Fri 16 OctChur 20:56+3 min+3 min
Thu 15 OctChur 20:52−1 min—
Wed 14 OctChur 20:540 min—
Tue 13 OctChur 20:52−2 min—
Mon 12 OctChur 20:530 min—
Sun 11 OctChur 20:53No data—
Sat 10 OctChur 20:540 min—
Fri 9 OctChur 20:53−1 min—
Thu 8 OctChur 20:530 min—
Wed 7 OctChur 20:530 min—