Train NS Int 10143 Amsterdam Centraal → Woerden
NS Int 10143 Amsterdam Centraal–Woerden: too few runs with delay data yet to give its punctuality (1 in the last 30 days; 3 needed). TrainsRadar data as of 21 Nov 2026, 13:45 (GMT+1).
An alert on this phone or computer when the 10143 is 5 min or more late, every day it runs. No account, no email.
✓ Today’s run finished
Today, last fix heading to Amsterdam Centraal at 07:48 0 min
- Amsterdam Centraal07:34
- Woerden07:59
Next service: Saturday 07:34 from Amsterdam Centraal · Sat 28 Nov
Last 30 days
Arrival delay at Woerden, 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
1 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 1
- 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
- 100% S n=1
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (2 stops).
Not enough runs yet to work out the usual delay by stop.
| Stop | Sched. |
|---|---|
| 07:34 | |
| 07:59 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Amsterdam Centraal 07:48Partial coverage | 0 min | — |
| Sat 26 Sept | Amsterdam Centraal 07:50 | No data | — |
| Sat 5 Sept | Amsterdam Centraal 07:48 | No data | — |
| Sat 29 Aug | Amsterdam Centraal 07:48 | No data | — |