Train NS 6750 Tiel – Bodegraven

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Friday 14:18 from Tiel · Fri 13 Nov

Next departure 14:18 Friday · Tiel
On-time · 30 days
86%
6/7 runs under 3 min
RT coverage: 4 full · 3 partial · 5 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 6 full · 3 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Sat 31 Oct Max en route +13 min · last fix heading to Woerden +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 0% · 0
  • 10–30 min 11% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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