K1 839103 Paris Est – Château-Thierry
Alerts for train 839103
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line K1.
It has not run yet today
Last recorded run: Friday 6 November 0 min
Next service: today 12:36 from Paris Est · Mon 9 Nov
Last 30 days
Arrival delay at Château-Thierry, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 22 Oct Max en route +90 min · last fix heading to Château-Thierry +80 min
- Thu 17 Sept Max en route +60 min · last fix heading to StopPoint:OCETrain TER-8711658 +45 min
- Tue 22 Sept Max en route +25 min · last fix heading to StopPoint:OCETrain TER-8717155 +15 min
- Mon 12 Oct Max en route +10 min · last fix heading to Château-Thierry +5 min
- Wed 23 Sept Max en route +5 min · last fix heading to StopPoint:OCETrain TER-8717400 +5 min
Distribution · 90 days
44 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 39
- 3–10 min 5% · 2
- 10–30 min 2% · 1
- 30+ min 5% · 2
On-time by weekday
- 90% M n=10
- 89% T n=9
- 89% W n=9
- 75% T n=8
- 100% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Last 90 days, 44 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 12:36 | on time | on time | |
| 13:29 | on time | +4 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Fri 6 Nov | Château-Thierry 13:29 | 0 min | — |
| Wed 4 Nov | Château-Thierry 13:29 | 0 min | — |
| Tue 3 Nov | Château-Thierry 13:30 | 0 min | — |
| Mon 2 Nov | Château-Thierry 13:29 | 0 min | — |
| Fri 30 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Thu 29 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Wed 28 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Tue 27 Oct | Châlons-en-Champagne 14:14 | 0 min | +5 min |
| Mon 26 Oct | Châlons-en-Champagne 14:15 | 0 min | — |
| Thu 22 Oct | Château-Thierry 14:50 | +80 min | +90 min |
| Wed 21 Oct | Château-Thierry 13:30 | 0 min | — |
| Tue 20 Oct | Château-Thierry 13:31 | 0 min | — |
| Mon 19 Oct | Château-Thierry 13:30 | 0 min | — |
| Fri 16 Oct | Château-Thierry 13:30 | 0 min | — |
| Thu 15 Oct | Château-Thierry 13:30 | 0 min | +5 min |
| Wed 14 Oct | Château-Thierry 13:30 | 0 min | — |
| Tue 13 Oct | Château-Thierry 13:30 | 0 min | — |
| Mon 12 Oct | Château-Thierry 13:35 | +5 min | +10 min |
| Fri 9 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Thu 8 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Wed 7 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Tue 6 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Mon 5 Oct | Châlons-en-Champagne 14:14 | 0 min | — |
| Fri 2 Oct | StopPoint:OCETrain TER-8711658 13:28 | 0 min | — |
| Thu 1 Oct | StopPoint:OCETrain TER-8711658 13:28 | 0 min | +5 min |
| Wed 30 Sept | StopPoint:OCETrain TER-8711658 13:28 | 0 min | — |
| Tue 29 Sept | StopPoint:OCETrain TER-8711658 13:28 | 0 min | — |
| Mon 28 Sept | StopPoint:OCETrain TER-8711658 13:29 | 0 min | — |
| Thu 24 Sept | StopPoint:OCETrain TER-8717400 14:12 | 0 min | — |
| Wed 23 Sept | StopPoint:OCETrain TER-8717400 14:12 | +5 min | +5 min |