P75 839223 Fismes – Reims

View line P75

Fismes 18:34 → Reims 19:02 Mon, Tue, Thu, Fri 0 h 28 min · 6 stops SNCF

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:34 from Fismes · Mon 9 Nov

Next departure 18:34 today · Fismes
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 1 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 31 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 Reims, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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:34on time on time
18:38 / 18:39≈ on time ≈ on time
18:42 / 18:43≈ on time ≈ on time
18:46 / 18:47≈ on time ≈ on time
18:52 / 18:53≈ on time ≈ on time
19:02on 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 6 NovReims 19:040 min—
Thu 5 NovReims 19:03No data—
Wed 4 NovReims 19:030 min—
Tue 3 NovReims 19:040 min—
Mon 2 NovReims 19:030 min—
Fri 16 OctReims 19:030 min—
Thu 15 OctReims 19:030 min—
Wed 14 OctReims 19:030 min—
Tue 13 OctReims 19:030 min—
Mon 12 OctReims 19:030 min—
Fri 9 OctReims 19:030 min—
Thu 8 OctReims 19:030 min—
Tue 6 OctReims 19:030 min—
Mon 5 OctReims 19:030 min—
Fri 25 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Thu 24 SeptStopPoint:OCETrain TER-8717100 19:020 min+5 min
Wed 23 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Tue 22 SeptStopPoint:OCETrain TER-8717100 19:010 min+5 min
Mon 21 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Fri 18 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Thu 17 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Wed 16 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Tue 15 SeptStopPoint:OCETrain TER-8717100 19:010 min+25 min
Mon 14 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Fri 11 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Thu 10 SeptStopPoint:OCETrain TER-8717100 19:020 min—
Wed 9 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Tue 8 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Mon 7 SeptStopPoint:OCETrain TER-8717100 19:010 min—
Wed 2 SeptStopPoint:OCETrain TER-8717100 19:020 min—