K4 840863 Paris Est – Troyes

View line K4

Paris Est 15:12 → Troyes 16:44 Mon, Tue, Thu 1 h 32 min · 4 stops SNCF

It does not run today

Last recorded run: Monday 2 November 0 min

Next service: Monday 15:12 from Paris Est · Mon 9 Nov

Next departure 15:12 Monday · Paris Est
On-time · 30 days
71%
10/14 runs under 3 min
RT coverage: 14 full · 0 partial · 0 no data
On-time · 90 days
76%
28/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+20min
9 in 10 runs arrive with less than this
30 days: +14 min

Last 30 days

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

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

Worst days

  • Wed 23 Sept Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8711819 +50 min
  • Mon 5 Oct Max en route +25 min · last fix heading to Troyes +25 min
  • Thu 17 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8711815 +25 min
  • Thu 8 Oct Max en route +25 min · last fix heading to Troyes +20 min
  • Thu 3 Sept Max en route +20 min · last fix heading to StopPoint:OCETrain TER-8711800 +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 28
  • 3–10 min 5% · 2
  • 10–30 min 16% · 6
  • 30+ min 3% · 1

On-time by weekday

  • 80% M n=10
  • 100% T n=9
  • 67% W n=9
  • 56% T n=9
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 37 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
15:12on time +5 min
16:08 / 16:10≈ on time ≈ +14 min
16:20 / 16:21≈ on time ≈ +16 min
16:44on time +20 min

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
Mon 2 NovTroyes 16:440 min+5 min
Thu 29 OctTroyes 16:450 min—
Wed 28 OctTroyes 16:50+5 min+5 min
Tue 27 OctTroyes 17:150 min—
Mon 26 OctTroyes 16:460 min—
Thu 22 OctTroyes 17:01+15 min+15 min
Wed 21 OctTroyes 16:450 min—
Tue 20 OctTroyes 16:450 min—
Mon 19 OctTroyes 16:460 min—
Thu 15 OctTroyes 16:450 min—
Wed 14 OctTroyes 16:450 min—
Tue 13 OctTroyes 16:450 min—
Mon 12 OctTroyes 16:50+10 min+10 min
Thu 8 OctTroyes 17:05+20 min+25 min
Wed 7 OctTroyes 16:450 min+5 min
Tue 6 OctTroyes 16:450 min—
Mon 5 OctTroyes 17:10+25 min+25 min
Thu 1 OctStopPoint:OCETrain TER-8711800 16:430 min—
Wed 30 SeptStopPoint:OCETrain TER-8711800 16:43+5 min+5 min
Tue 29 SeptStopPoint:OCETrain TER-8711800 16:430 min+5 min
Mon 28 SeptStopPoint:OCETrain TER-8711800 16:430 min+5 min
Thu 24 SeptStopPoint:OCETrain TER-8711800 16:410 min+5 min
Wed 23 SeptStopPoint:OCETrain TER-8711819 16:42+50 min+60 min
Tue 22 SeptStopPoint:OCETrain TER-8711800 16:420 min—
Mon 21 SeptStopPoint:OCETrain TER-8711800 16:410 min—
Thu 17 SeptStopPoint:OCETrain TER-8711815 16:41+25 min+25 min
Wed 16 SeptStopPoint:OCETrain TER-8711800 16:420 min—
Tue 15 SeptStopPoint:OCETrain TER-8711800 16:420 min—
Mon 14 SeptStopPoint:OCETrain TER-8711800 16:410 min—
Thu 10 SeptStopPoint:OCETrain TER-8711800 16:420 min—