C10 831419 Colmar – Mulhouse

View line C10

Colmar 14:12 → Mulhouse 14:40 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 5 stops SNCF

✓ Today’s run finished

Today it reached Mulhouse at 14:40 0 min

  1. Colmar14:12
  2. Rouffach14:19
  3. Bollwiller14:27
  4. Mulhouse Dornach14:35
  5. Mulhouse14:40

Next service: tomorrow 14:12 from Colmar · Thu 19 Nov

Next departure 14:12 tomorrow · Colmar
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 3 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 25 full · 4 partial · 11 no data
Typical delay
0min
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 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

  • Tue 3 Nov Max en route +10 min · last fix heading to Mulhouse +10 min
  • Mon 28 Sept Max en route +10 min · last fix heading to Mulhouse Dornach +10 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Mulhouse +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 3% · 1
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 89% T n=9
  • 86% W n=7
  • 100% T n=2
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 29 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:12on time on time
14:19 / 14:20≈ on time ≈ +1 min
14:27≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:40on time 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
Wed 18 NovMulhouse 14:390 min+5 min
Tue 17 NovMulhouse 14:390 min—
Mon 16 NovMulhouse 14:39No data—
Fri 13 NovMulhouse 14:390 min—
Thu 12 NovMulhouse 14:420 min—
Tue 10 NovMulhouse 14:390 min—
Mon 9 NovMulhouse 14:390 min—
Fri 6 NovMulhouse 14:390 min—
Thu 5 NovMulhouse 14:39No data—
Wed 4 NovMulhouse 14:390 min—
Tue 3 NovMulhouse 14:49+10 min+10 min
Mon 2 NovMulhouse 14:39No data—
Fri 16 OctMulhouse 14:420 min—
Thu 15 OctMulhouse 14:41No data—
Wed 14 OctMulhouse 14:46+5 min+5 min
Tue 13 OctMulhouse 14:410 min—
Mon 12 OctMulhouse 14:41No data—
Fri 9 OctMulhouse 14:410 min—
Thu 8 OctMulhouse 14:410 min—
Wed 7 OctMulhouse 14:410 min—
Tue 6 OctMulhouse 14:410 min—
Mon 5 OctMulhouse 14:420 min—
Thu 1 OctMulhouse 17:10No data—
Wed 30 SeptMulhouse 17:090 min—
Tue 29 SeptMulhouse 20:09No data—
Mon 28 SeptMulhouse Dornach 20:09Partial coverage+10 min+10 min
Fri 25 SeptMulhouse 20:100 min—
Thu 24 SeptRouffach 16:47Partial coverageNo data—
Wed 23 SeptRouffach 16:47Partial coverage0 min—
Tue 22 SeptRouffach 16:47Partial coverage0 min—