C52 23724 Forbach – Metz

View line C52

Forbach 06:06 → Metz 06:55 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 8 stops SNCF

Cancelled today · The operator has cancelled this train today. It is not running.

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: tomorrow 06:06 from Forbach · Fri 6 Nov

Next departure 06:06 tomorrow · Forbach
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 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 Metz, in minutes. One bar per run.

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

Worst days

  • Mon 12 Oct Max en route +5 min · last fix heading to Metz +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
06:06on time on time
06:12 / 06:13≈ on time ≈ on time
06:19 / 06:20≈ on time ≈ on time
06:24 / 06:25≈ on time ≈ on time
06:28 / 06:29≈ on time ≈ on time
06:35 / 06:36≈ on time ≈ on time
06:40 / 06:41≈ on time ≈ on time
06:55on 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 4 NovMetz 06:540 min—
Tue 3 NovMetz 06:540 min—
Mon 2 NovMetz 06:540 min—
Fri 30 OctMetz 06:560 min—
Thu 29 OctMetz 06:560 min—
Wed 28 OctMetz 06:560 min—
Tue 27 OctMetz 06:560 min+5 min
Mon 26 OctMetz 06:560 min—
Fri 23 OctMetz 06:560 min—
Thu 22 OctMetz 06:560 min—
Wed 21 OctMetz 06:560 min—
Tue 20 OctMetz 06:560 min—
Mon 19 OctMetz 06:560 min—
Fri 16 OctMetz 06:560 min—
Thu 15 OctMetz 06:560 min—
Wed 14 OctMetz 06:560 min—
Tue 13 OctMetz 06:560 min—
Mon 12 OctMetz 07:01+5 min+5 min
Fri 9 OctMetz 06:560 min—
Thu 8 OctMetz 06:560 min—
Wed 7 OctMetz 06:560 min—
Tue 6 OctMetz 06:570 min—
Mon 5 OctStopPoint:OCETrain TE~9ec4c9c1 06:570 min—
Mon 28 SeptStopPoint:OCETrain TER-8719203 06:540 min—