Train NS Int 9115 Amsterdam Centraal – London St. Pancras Int.

Amsterdam Centraal 06:40 → London St. Pancras Int. 10:57 Mon, Tue, Wed, Thu, Fri 4 h 17 min · 5 stops NS Int

✓ Today’s run finished

Today, last fix heading to Rotterdam Centraal at 07:42 No data

  1. Amsterdam Centraal06:40
  2. Rotterdam Centraal07:23
  3. Brussel-Zuid08:38
  4. Lille Europe09:25
  5. London St. Pancras Int.10:57

Next service: tomorrow 06:40 from Amsterdam Centraal · Fri 6 Nov

Next departure 06:40 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 13 full · 8 partial · 1 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 14 full · 8 partial · 39 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 London St. Pancras Int., 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
06:40on time on time
07:23 / 07:28≈ on time ≈ on time
08:38 / 08:51≈ on time ≈ on time
09:25 / 09:35≈ on time ≈ on time
10:57on 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
Thu 5 NovRotterdam Centraal 07:42No data—
Wed 4 NovRotterdam Centraal 07:42Partial coverage0 min—
Tue 3 NovRotterdam Centraal 07:42Partial coverage0 min—
Mon 2 NovRotterdam Centraal 07:54Partial coverage0 min—
Fri 30 OctRotterdam Centraal 07:53Partial coverage0 min—
Thu 29 OctRotterdam Centraal 07:42Partial coverage0 min—
Wed 28 OctRotterdam Centraal 08:03Partial coverage0 min—
Tue 27 OctRotterdam Centraal 07:42Partial coverage0 min—
Mon 26 OctRotterdam Centraal 07:55Partial coverage0 min—
Fri 23 OctRotterdam Centraal 07:420 min—
Thu 22 OctRotterdam Centraal 07:420 min—
Wed 21 OctRotterdam Centraal 07:500 min—
Tue 20 OctRotterdam Centraal 07:420 min—
Mon 19 OctRotterdam Centraal 07:510 min—
Fri 16 OctRotterdam Centraal 07:430 min—
Thu 15 OctRotterdam Centraal 07:510 min—
Wed 14 OctRotterdam Centraal 07:540 min—
Tue 13 OctRotterdam Centraal 07:420 min—
Mon 12 OctRotterdam Centraal 07:520 min—
Fri 9 OctRotterdam Centraal 07:460 min—
Thu 8 OctRotterdam Centraal 07:420 min—
Wed 7 OctRotterdam Centraal 07:420 min—
Tue 6 OctRotterdam Centraal 07:450 min—
Mon 5 OctRotterdam Centraal 07:45No data—
Fri 2 OctRotterdam Centraal 07:42No data—
Thu 1 OctRotterdam Centraal 07:42No data—
Wed 30 SeptRotterdam Centraal 07:42No data—
Tue 29 SeptRotterdam Centraal 07:50No data—
Mon 28 SeptRotterdam Centraal 07:43No data—
Fri 25 SeptRotterdam Centraal 07:42No data—