Train NS 6770 Tiel – Leiden Centraal

Tiel 19:18 → Leiden Centraal 20:37 Mon, Fri, Sat, Sun 1 h 19 min · 14 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Leiden Lammenschans at 20:47 0 min

  1. Tiel19:18
  2. Geldermalsen19:29
  3. Houten Castellum19:41
  4. Utrecht Vaartsche Rijn19:52
  5. Woerden20:06
  6. Leiden Lammenschans20:32
  7. Leiden Centraal20:37

Next service: tomorrow 19:18 from Tiel · Sun 11 Oct

Full trip card
Next departure 19:18 tomorrow · Tiel
On-time · 30 days
67%
2/3 runs under 3 min
RT coverage: 2 full · 1 partial · 8 no data
On-time · 90 days
67%
2/3 runs under 3 min
RT coverage: 2 full · 1 partial · 29 no data
Typical delay
—
Needs at least 5 runs with data (3 so far)
P90
—
Needs at least 5 runs with data (3 so far)

Last 30 days

Arrival delay at Leiden 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

  • Mon 5 Oct Max en route +12 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 67% · 2
  • 3–10 min 0% · 0
  • 10–30 min 33% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

StopSched.
Tiel
19:18
Tiel Passewaaij
19:21
Geldermalsen
19:29 / 19:30
Culemborg
19:35
Houten Castellum
19:41 / 19:42
Houten
19:45
Utrecht Lunetten
19:49
Utrecht Vaartsche Rijn
19:52
Utrecht Centraal
19:55 / 19:56
Woerden
20:06 / 20:07
Bodegraven
20:15 / 20:16
Alphen a/d Rijn
20:23 / 20:24
Leiden Lammenschans
20:32
Leiden Centraal
20:37

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

DateLast stopFinalMax
Sat 10 OctLeiden Lammenschans 20:47Partial coverage0 min—
Fri 9 Oct— 20:38+1 min—
Mon 5 Oct— 20:50+11 min+12 min
Sun 4 OctLeiden Lammenschans 20:47No data—
Sat 3 OctLeiden Lammenschans 20:51No data—
Sun 27 SeptLeiden Lammenschans 21:01No data—
Sat 26 SeptLeiden Lammenschans 20:56No data—
Sun 20 SeptLeiden Lammenschans 20:49No data—
Sat 19 SeptLeiden Lammenschans 20:47No data—
Sun 13 SeptLeiden Lammenschans 20:48No data—
Sat 12 SeptLeiden Lammenschans 21:01No data—
Sun 6 SeptLeiden Lammenschans 20:47No data—
Sat 5 SeptLeiden Lammenschans 20:47No data—
Sun 30 AugLeiden Lammenschans 20:47No data—
Sat 29 AugLeiden Lammenschans 20:47No data—
Fri 28 AugGeldermalsen 19:44No data—
Sun 23 AugUtrecht Vaartsche Rijn 20:22No data—
Sat 22 AugUtrecht Vaartsche Rijn 20:22No data—
Fri 21 AugUtrecht Vaartsche Rijn 20:04No data—
Wed 19 AugTiel Passewaaij 19:40No data—
Sun 16 AugLeiden Lammenschans 20:47No data—
Sat 15 AugLeiden Lammenschans 20:48No data—
Fri 14 AugLeiden Lammenschans 20:46No data—
Sun 9 AugBodegraven 20:30No data—
Sat 8 AugBodegraven 20:30No data—
Fri 7 AugBodegraven 20:30No data—
Sun 2 AugLeiden Lammenschans 20:48No data—
Sat 1 AugLeiden Lammenschans 20:47No data—
Fri 31 JulLeiden Lammenschans 20:46No data—
Sun 26 JulLeiden Lammenschans 20:47No data—