C23+ 831622 Strasbourg – Molsheim

View line C23+

Strasbourg 14:56 → Molsheim 15:12 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 3 stops SNCF

✓ Today’s run finished

Today it reached Molsheim at 15:12 0 min

  1. Strasbourg14:56
  2. Entzheim Aéroport15:04
  3. Molsheim15:12

Next service: tomorrow 14:56 from Strasbourg · Wed 11 Nov

Next departure 14:56 tomorrow · Strasbourg
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 2 no data
On-time · 90 days
100%
44/44 runs under 3 min
RT coverage: 44 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Molsheim, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 44
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=10
  • 100% W n=8
  • 100% T n=9
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 44 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:56on time on time
15:04 / 15:05≈ on time ≈ on time
15:12on 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
Tue 10 NovMolsheim 15:130 min—
Mon 9 NovMolsheim 15:130 min—
Fri 6 NovBarr 15:42No data—
Thu 5 NovBarr 15:420 min—
Wed 4 NovBarr 15:42No data—
Tue 3 NovBarr 15:430 min—
Fri 16 OctBarr 15:420 min—
Thu 15 OctBarr 15:420 min—
Wed 14 OctBarr 15:420 min—
Tue 13 OctBarr 15:420 min—
Mon 12 OctBarr 15:420 min—
Fri 9 OctBarr 15:420 min—
Thu 8 OctBarr 15:420 min—
Wed 7 OctBarr 15:420 min—
Tue 6 OctBarr 15:420 min—
Mon 5 OctBarr 15:420 min—
Fri 2 OctStopPoint:OCETrain TER-8721424 15:400 min—
Thu 1 OctStopPoint:OCETrain TER-8721424 15:410 min—
Wed 30 SeptStopPoint:OCETrain TER-8721424 15:400 min+5 min
Tue 29 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Mon 28 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Fri 25 SeptStopPoint:OCETrain TER-8721424 15:410 min—
Thu 24 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Wed 23 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Tue 22 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Mon 21 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Fri 18 SeptStopPoint:OCETrain TER-8721424 15:410 min—
Thu 17 SeptStopPoint:OCETrain TER-8721424 15:400 min—
Wed 16 SeptStopPoint:OCETrain TER-8721424 15:410 min—
Tue 15 SeptStopPoint:OCETrain TER-8721424 15:400 min—