C52 23810 Forbach – Metz

View line C52

Forbach 18:33 → Metz 19:21 Wed, Sun 0 h 48 min · 7 stops SNCF

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 18:33 from Forbach · Sun 8 Nov

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

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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 9 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
18:33on time +1 min
18:39 / 18:40≈ on time ≈ +1 min
18:47 / 18:48≈ on time ≈ +1 min
18:54 / 18:55≈ on time ≈ +1 min
19:02≈ on time ≈ on time
19:07 / 19:08≈ on time ≈ on time
19:21on 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
Sun 1 NovMetz 19:220 min—
Sun 25 OctMetz 19:220 min—
Sun 18 OctMetz 19:220 min—
Sun 11 OctMetz 19:220 min—
Sun 4 OctStopPoint:OCETrain TE~9ec4c9c1 19:230 min—
Wed 30 SeptStopPoint:OCETrain TER-8719203 19:20No data—
Wed 23 SeptStopPoint:OCETrain TER-8719203 19:20No data—
Sun 20 SeptStopPoint:OCETrain TER-8719203 19:210 min—
Wed 16 SeptStopPoint:OCETrain TER-8719203 19:20No data—
Sun 13 SeptStopPoint:OCETrain TER-8719203 19:200 min—
Wed 9 SeptStopPoint:OCETrain TER-8719203 19:20No data—
Sun 6 SeptStopPoint:OCETrain TER-8719203 19:200 min—
Wed 26 AugStopPoint:OCETrain TER-8719203 19:20No data—
Sun 16 AugStopPoint:OCETrain TER-8719203 19:210 min+5 min