Train NS Int 140 4195843 – Amsterdam Centraal

4195843 14:57 → Amsterdam Centraal 22:01 Daily 7 h 04 min · 15 stops NS Int

It has not run yet today

Last recorded run: Sunday 1 November 0 min

Next service: today 14:57 from 4195843 · Thu 5 Nov

Next departure 14:57 today · 4195843
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 2 full · 2 partial · 2 no data
On-time · 90 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
P90
+17min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Amsterdam Centraal, in minutes. One bar per run.

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

Worst days

  • Sun 18 Oct Max en route +28 min · last fix heading to Utrecht Centraal +27 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 4
  • 3–10 min 0% · 0
  • 10–30 min 20% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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
14:57on time on time
15:04 / 15:09— —
15:18 / 15:19— —
15:59 / 16:01— —
16:53 / 16:56— —
17:10 / 17:18— —
19:09 / 19:11— —
19:34 / 19:36— —
19:48 / 19:51— —
20:07 / 20:09— —
20:41 / 20:48— —
20:58 / 21:00— —
21:24 / 21:26— —
21:37 / 21:39— —
22:01— —

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
Sun 1 NovHilversum 21:53Partial coverage0 min—
Sat 31 OctHilversum 21:53Partial coverage0 min—
Sun 18 OctUtrecht Centraal 23:15+27 min+28 min
Sat 17 OctUtrecht Centraal 02:120 min—
Sun 11 OctHilversum 21:53No data—
Sat 10 OctHilversum 21:53No data—
Sun 4 OctApeldoorn 21:46No data—
Sat 3 OctApeldoorn 21:56No data—
Sun 27 SeptApeldoorn 21:41No data—
Sat 26 SeptAmersfoort Centraal 21:49No data—
Sun 20 SeptHilversum 22:15No data—
Sat 19 SeptHilversum 21:54No data—
Mon 14 SeptAmersfoort Centraal 19:01+1 min+3 min
Sun 13 SeptAmersfoort Centraal 21:42No data—
Sat 12 SeptAmersfoort Centraal 21:57No data—
Sun 6 SeptAmersfoort Centraal 21:57No data—
Sat 5 SeptAmersfoort Centraal 21:43No data—
Sun 30 AugAmersfoort Centraal 21:49No data—
Sat 29 AugAmersfoort Centraal 22:17No data—
Sun 23 AugUtrecht Centraal 23:26No data—
Sat 22 AugHilversum 22:12No data—
Fri 21 AugHengelo 20:54No data—
Sun 16 AugHilversum 23:03No data—
Sat 15 AugHilversum 22:51No data—
Fri 14 AugHengelo 21:02No data—
Thu 13 AugHengelo 21:42No data—
Wed 12 AugHengelo 20:48No data—
Tue 11 AugHengelo 20:46No data—
Sun 9 AugHilversum 22:21No data—
Sat 8 AugHilversum 22:37No data—