Train NS 6722 Tiel – Bodegraven

Tiel 07:18 → Bodegraven 08:15 Fri, Sat, Sun 0 h 57 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Woerden at 08:19 0 min

  1. Tiel07:18
  2. Geldermalsen07:29
  3. Culemborg07:35
  4. Houten07:45
  5. Utrecht Vaartsche Rijn07:52
  6. Woerden08:06
  7. Bodegraven08:15

Next service: tomorrow 07:18 from Tiel · Sun 15 Nov

Full trip card
Next departure 07:18 tomorrow · Tiel
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 3 full · 6 partial · 2 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 6 full · 6 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Bodegraven, 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

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

  • Early 0% · 0
  • On time 100% · 12
  • 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
  • 100% F n=5
  • 100% S n=5
  • 100% S n=2

Stops and timetable

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

Last 90 days, 12 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
Tiel
07:18on time on time
Tiel Passewaaij
07:21≈ on time ≈ on time
Geldermalsen
07:29 / 07:30≈ on time ≈ on time
Culemborg
07:35≈ on time ≈ on time
Houten Castellum
07:41 / 07:42≈ on time ≈ on time
Houten
07:45≈ on time ≈ +1 min
Utrecht Lunetten
07:49≈ on time ≈ +1 min
Utrecht Vaartsche Rijn
07:52≈ on time ≈ +1 min
Utrecht Centraal
07:55 / 07:56≈ on time ≈ +1 min
Woerden
08:06 / 08:07≈ on time ≈ +1 min
Bodegraven
08:15on time +1 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

DateLast stopFinalMax
Sat 14 NovWoerden 08:19Partial coverage0 min—
Fri 13 NovWoerden 08:19Partial coverage0 min—
Fri 6 NovUtrecht Centraal 08:54No data—
Sun 1 NovWoerden 08:22+1 min+1 min
Sat 31 OctWoerden 08:22Partial coverage0 min—
Fri 30 OctWoerden 08:21Partial coverage0 min—
Sun 25 OctWoerden 08:21No data—
Sat 24 OctWoerden 08:180 min—
Fri 23 OctWoerden 08:200 min—
Sat 17 OctWoerden 08:21Partial coverage0 min—
Fri 16 OctWoerden 08:21Partial coverage0 min—
Sun 11 OctLeiden Lammenschans 08:470 min—
Sat 10 OctLeiden Lammenschans 08:480 min—
Fri 9 OctLeiden Lammenschans 08:49+2 min+6 min
Mon 5 OctLeiden Lammenschans 08:50No data—
Sun 4 OctLeiden Lammenschans 08:48No data—
Sat 3 OctLeiden Lammenschans 08:47No data—
Fri 2 OctLeiden Lammenschans 08:47No data—
Sun 27 SeptLeiden Lammenschans 08:48No data—
Sat 26 SeptLeiden Lammenschans 08:48No data—
Fri 25 SeptLeiden Lammenschans 08:47No data—
Sun 20 SeptLeiden Lammenschans 08:49No data—
Sat 19 SeptLeiden Lammenschans 08:47No data—
Fri 18 SeptLeiden Lammenschans 08:47No data—
Sun 13 SeptLeiden Lammenschans 08:48No data—
Sat 12 SeptLeiden Lammenschans 08:48No data—
Fri 11 SeptLeiden Lammenschans 08:48No data—
Sun 6 SeptLeiden Lammenschans 08:47No data—
Sat 5 SeptLeiden Lammenschans 08:47No data—
Fri 4 SeptLeiden Lammenschans 08:48No data—