P15 831114 Colmar → Metzeral

View line P15

Colmar 11:12 → Metzeral 11:47 Mon, Tue, Wed, Thu, Fri 0 h 35 min · 10 stops SNCF

TER 831114 Colmar–Metzeral: final delay under 3 min on 13 of its 13 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 07:35 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 11:12 from Colmar · Mon 23 Nov

Next departure 11:12 tomorrow · Colmar
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 1 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 1 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 Metzeral, 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

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

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

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
11:12on time on time
11:14≈ on time ≈ on time
11:17≈ on time ≈ on time
11:21 / 11:23≈ on time ≈ on time
11:28 / 11:29≈ on time ≈ on time
11:34 / 11:36≈ on time ≈ on time
11:38≈ on time ≈ on time
11:40 / 11:41≈ on time ≈ on time
11:43≈ on time ≈ on time
11:47on 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
Fri 20 NovMetzeral 11:480 min—
Thu 19 NovMetzeral 11:480 min—
Wed 18 NovMetzeral 11:480 min—
Tue 17 NovMetzeral 11:480 min—
Mon 16 NovMetzeral 11:490 min—
Fri 13 NovMetzeral 11:480 min—
Thu 12 NovMetzeral 11:480 min—
Wed 11 NovMetzeral 11:48No data—
Tue 10 NovMetzeral 11:480 min—
Mon 9 NovMetzeral 11:490 min—
Fri 6 NovMetzeral 11:480 min—
Wed 4 NovMetzeral 11:480 min—
Tue 3 NovMetzeral 11:480 min—
Mon 2 NovMetzeral 11:480 min—
Fri 16 OctMetzeral 11:480 min—
Thu 15 OctMetzeral 11:480 min—
Wed 14 OctMetzeral 11:480 min—
Tue 13 OctMetzeral 11:480 min—
Mon 12 OctMetzeral 11:490 min—
Fri 9 OctMetzeral 11:490 min—
Thu 8 OctMetzeral 11:480 min—
Wed 7 OctMetzeral 11:480 min—
Tue 6 OctMetzeral 11:480 min—
Mon 5 OctStopPoint:OCETrain TE~66bbf0b1 11:480 min—