K2 839136 Château-Thierry – Paris Est

View line K2

Château-Thierry 10:59 → Paris Est 11:53 Mon, Tue, Wed, Thu, Fri 0 h 54 min · 2 stops SNCF

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 10:59 from Château-Thierry · Mon 9 Nov

Next departure 10:59 tomorrow · Château-Thierry
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 11 full · 0 partial · 8 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 14 full · 0 partial · 20 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 Paris Est, 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 21 Oct Max en route +5 min · last fix heading to Paris Est +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=2
  • 50% W n=2
  • 100% T n=2
  • 100% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
10:59on time on time
11:53on 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 NovParis Est 11:54No data—
Thu 5 NovParis Est 11:54No data—
Wed 4 NovParis Est 11:54No data—
Tue 3 NovParis Est 11:55No data—
Mon 2 NovParis Est 11:540 min—
Fri 30 OctParis Est 11:54No data—
Thu 29 OctParis Est 11:54No data—
Wed 28 OctParis Est 11:54No data—
Tue 27 OctParis Est 11:54No data—
Mon 26 OctParis Est 11:540 min+5 min
Thu 22 OctParis Est 11:540 min—
Wed 21 OctParis Est 11:59+5 min+5 min
Tue 20 OctParis Est 11:540 min—
Mon 19 OctParis Est 11:540 min—
Fri 16 OctParis Est 11:540 min—
Thu 15 OctParis Est 11:540 min—
Wed 14 OctParis Est 11:540 min—
Tue 13 OctParis Est 11:540 min—
Mon 12 OctParis Est 11:550 min—
Fri 9 OctParis Est 11:54No data—
Thu 8 OctParis Est 11:54No data—
Wed 7 OctParis Est 11:54No data—
Tue 6 OctParis Est 12:02No data—
Mon 5 OctStopPoint:OCETrain TE~91aa7299 11:540 min—
Fri 2 OctStopPoint:OCETrain TER-8711300 11:52No data—
Thu 1 OctStopPoint:OCETrain TER-8711300 11:52No data—
Wed 30 SeptStopPoint:OCETrain TER-8711300 11:53No data—
Tue 29 SeptStopPoint:OCETrain TER-8711300 11:52No data—
Mon 28 SeptStopPoint:OCETrain TER-8711300 11:520 min—
Mon 17 AugStopPoint:OCETrain TER-8711300 11:520 min+5 min