Train NS 6734 Tiel → Bodegraven

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

NS 6734 Tiel–Bodegraven: final delay under 3 min on 8 of its 9 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 05:07 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 10:18 from Tiel · Sun 22 Nov

Next departure 10:18 today · Tiel
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 1 full · 8 partial · 2 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 5 full · 9 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: +4 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

Worst days

  • Sun 1 Nov Max en route +17 min · last fix heading to Woerden +17 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
10:18on time on time
10:21≈ on time ≈ on time
10:29 / 10:30≈ on time ≈ on time
10:35≈ on time ≈ on time
10:41 / 10:42≈ on time ≈ on time
10:45≈ on time ≈ on time
10:49≈ on time ≈ on time
10:52≈ on time ≈ on time
10:55 / 10:56≈ on time ≈ on time
11:06 / 11:07≈ on time ≈ +1 min
11: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 21 NovWoerden 11:19Partial coverage0 min—
Fri 20 NovWoerden 11:19Partial coverage0 min—
Sun 15 NovWoerden 11:19Partial coverage0 min—
Sat 14 NovWoerden 11:19Partial coverage0 min—
Fri 13 NovWoerden 11:19Partial coverage0 min—
Fri 6 NovWoerden 11:24No data—
Sun 1 NovWoerden 11:44Partial coverage+17 min+17 min
Sat 31 OctWoerden 11:21Partial coverage0 min—
Fri 30 OctWoerden 11:21Partial coverage0 min—
Sun 25 OctWoerden 11:21No data—
Sat 24 OctWoerden 11:180 min—
Fri 23 OctWoerden 11:21No data—
Sun 18 OctUtrecht Vaartsche Rijn 11:060 min—
Sat 17 OctWoerden 11:23Partial coverage0 min—
Fri 16 OctWoerden 11:22No data—
Sun 11 OctLeiden Lammenschans 11:47+1 min—
Sat 10 OctLeiden Lammenschans 11:470 min—
Fri 9 OctLeiden Lammenschans 11:480 min+1 min
Mon 5 OctLeiden Lammenschans 11:47No data—
Sun 4 OctLeiden Lammenschans 11:47No data—
Sat 3 OctLeiden Lammenschans 11:48No data—
Fri 2 OctLeiden Lammenschans 11:47No data—
Sun 27 SeptLeiden Lammenschans 11:47No data—
Sat 26 SeptLeiden Lammenschans 11:47No data—
Fri 25 SeptLeiden Lammenschans 11:48No data—
Sun 20 SeptLeiden Lammenschans 11:47No data—
Sat 19 SeptLeiden Lammenschans 11:47No data—
Fri 18 SeptLeiden Lammenschans 11:47No data—
Sun 13 SeptLeiden Lammenschans 11:47No data—
Sat 12 SeptLeiden Lammenschans 11:47No data—