Train NS 6723 Bodegraven – Tiel

Bodegraven 07:16 → Tiel 08:12 Fri, Sat, Sun 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tiel Passewaaij at 08:23 0 min

  1. Bodegraven07:16
  2. Utrecht Centraal07:33
  3. Utrecht Vaartsche Rijn07:37
  4. Houten07:43
  5. Culemborg07:53
  6. Tiel Passewaaij08:08
  7. Tiel08:12

Next service: tomorrow 07:16 from Bodegraven · Sun 15 Nov

Next departure 07:16 tomorrow · Bodegraven
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 3 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 7 full · 5 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Tiel, in minutes. One bar per run.

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

Worst days

  • Fri 9 Oct Max en route +6 min · last fix heading to Tiel Passewaaij +6 min

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 92% · 11
  • 3–10 min 8% · 1
  • 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
  • 75% F n=4
  • 100% S n=5
  • 100% S n=3

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
07:16on time on time
07:23≈ on time ≈ on time
07:33 / 07:35≈ on time ≈ +1 min
07:37≈ on time ≈ +1 min
07:40≈ on time ≈ +1 min
07:43 / 07:44≈ on time ≈ +1 min
07:47≈ on time ≈ +2 min
07:53≈ on time ≈ +2 min
08:00 / 08:01≈ on time ≈ +2 min
08:08≈ on time ≈ +3 min
08:12on time +3 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 NovTiel Passewaaij 08:23Partial coverage0 min—
Fri 13 NovTiel Passewaaij 08:23Partial coverage+1 min—
Fri 6 NovTiel Passewaaij 08:24No data—
Sun 1 NovTiel Passewaaij 08:23+1 min—
Sat 31 OctTiel Passewaaij 08:24Partial coverage+2 min+2 min
Fri 30 OctTiel Passewaaij 08:23Partial coverage0 min—
Sun 25 OctTiel Passewaaij 08:24No data—
Sat 24 OctZaltbommel 08:320 min—
Fri 23 OctZaltbommel 08:320 min—
Sun 18 OctTiel Passewaaij 08:230 min—
Sat 17 OctTiel Passewaaij 08:24Partial coverage+2 min+2 min
Fri 16 OctTiel Passewaaij 08:24No data—
Sun 11 OctTiel Passewaaij 08:23+1 min—
Sat 10 OctTiel Passewaaij 08:220 min—
Fri 9 OctTiel Passewaaij 08:28+6 min+6 min
Mon 5 OctTiel Passewaaij 08:29No data—
Sun 4 OctTiel Passewaaij 08:23No data—
Sat 3 OctTiel Passewaaij 08:23No data—
Fri 2 OctTiel Passewaaij 08:24No data—
Sun 27 SeptTiel Passewaaij 08:26No data—
Sat 26 SeptTiel Passewaaij 08:24No data—
Fri 25 SeptTiel Passewaaij 08:23No data—
Sun 20 SeptTiel Passewaaij 08:23No data—
Sat 19 SeptTiel Passewaaij 08:23No data—
Fri 18 SeptTiel Passewaaij 08:23No data—
Sun 13 SeptTiel Passewaaij 08:23No data—
Sat 12 SeptTiel Passewaaij 08:23No data—
Fri 11 SeptTiel Passewaaij 08:23No data—
Sun 6 SeptTiel Passewaaij 08:23No data—
Sat 5 SeptTiel Passewaaij 08:23No data—