C10 831423 Colmar – Mulhouse

View line C10

Colmar 16:42 → Mulhouse 17:10 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 5 stops SNCF

✓ Today’s run finished

Today it reached Mulhouse at 17:15 +5 min

  1. Colmar16:42
  2. Rouffach16:49
  3. Bollwiller16:57
  4. Mulhouse Dornach17:05
  5. Mulhouse17:10

Next service: tomorrow 16:42 from Colmar · Tue 17 Nov

Next departure 16:42 tomorrow · Colmar
On-time · 30 days
75%
15/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
65%
34/52 runs under 3 min
RT coverage: 52 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Mulhouse, 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 23 Oct Max en route +35 min · last fix heading to Mulhouse +35 min
  • Tue 6 Oct Max en route +25 min · last fix heading to Mulhouse +25 min
  • Fri 6 Nov Max en route +15 min · last fix heading to Mulhouse +12 min
  • Mon 16 Nov Max en route +5 min · last fix heading to Mulhouse +5 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Mulhouse +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 34
  • 3–10 min 29% · 15
  • 10–30 min 4% · 2
  • 30+ min 2% · 1

On-time by weekday

  • 67% M n=12
  • 67% T n=9
  • 67% W n=9
  • 64% T n=11
  • 64% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 52 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
16:42on time +5 min
16:49 / 16:50≈ on time ≈ +5 min
16:57≈ on time ≈ +5 min
17:05≈ on time ≈ +5 min
17:10on time +5 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
Mon 16 NovMulhouse 17:14+5 min+5 min
Fri 13 NovMulhouse 17:100 min+5 min
Thu 12 NovMulhouse 17:090 min—
Tue 10 NovMulhouse 17:090 min—
Mon 9 NovMulhouse 17:090 min—
Fri 6 NovMulhouse 17:23+12 min+15 min
Thu 5 NovMulhouse 17:090 min+5 min
Wed 4 NovMulhouse 17:090 min—
Tue 3 NovMulhouse 17:100 min—
Mon 2 NovMulhouse 17:090 min—
Fri 30 OctMulhouse 17:110 min—
Thu 29 OctMulhouse 17:110 min+5 min
Wed 28 OctMulhouse 17:110 min—
Tue 27 OctMulhouse 17:16+5 min+5 min
Mon 26 OctMulhouse 17:120 min+5 min
Fri 23 OctMulhouse 17:47+35 min+35 min
Thu 22 OctMulhouse 17:17+5 min+5 min
Wed 21 OctMulhouse 17:120 min—
Tue 20 OctMulhouse 17:110 min—
Mon 19 OctMulhouse 17:120 min+5 min
Fri 16 OctMulhouse 17:110 min+5 min
Thu 15 OctMulhouse 17:110 min—
Wed 14 OctMulhouse 17:16+5 min+5 min
Tue 13 OctMulhouse 17:110 min—
Mon 12 OctMulhouse 17:110 min—
Fri 9 OctMulhouse 17:110 min—
Thu 8 OctMulhouse 17:110 min—
Wed 7 OctMulhouse 17:110 min—
Tue 6 OctMulhouse 17:36+25 min+25 min
Mon 5 OctMulhouse 17:16+5 min+5 min