Train NS 6762 Tiel – Bodegraven

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

It does not run today

Last recorded run: Sunday 1 November 0 min

Next service: tomorrow 17:18 from Tiel · Fri 6 Nov

Next departure 17:18 tomorrow · Tiel
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 6 full · 4 partial · 2 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 7 full · 4 partial · 28 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

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

  • Early 0% · 0
  • On time 100% · 11
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% 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, 11 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
17:18on time on time
17:21≈ on time ≈ on time
17:29 / 17:30≈ on time ≈ on time
17:35≈ on time ≈ on time
17:41 / 17:42≈ on time ≈ on time
17:45≈ on time ≈ on time
17:49≈ on time ≈ on time
17:52≈ on time ≈ on time
17:55 / 17:56≈ on time ≈ +1 min
18:06 / 18:07≈ on time ≈ +1 min
18: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
Sun 1 NovWoerden 18:20Partial coverage0 min—
Sat 31 OctWoerden 18:22Partial coverage+1 min—
Fri 30 OctWoerden 18:21Partial coverage0 min—
Sun 25 OctWoerden 18:26No data—
Sat 24 OctWoerden 18:190 min—
Fri 23 OctWoerden 18:210 min—
Sun 18 OctUtrecht Vaartsche Rijn 18:070 min—
Sat 17 OctWoerden 18:21Partial coverage0 min—
Fri 16 OctWoerden 18:22No data—
Sun 11 OctLeiden Lammenschans 18:470 min—
Sat 10 OctLeiden Lammenschans 18:470 min—
Fri 9 OctLeiden Lammenschans 18:46+1 min+2 min
Mon 5 OctWoerden 18:40+1 min+1 min
Sun 4 OctLeiden Lammenschans 18:47No data—
Sat 3 OctLeiden Lammenschans 18:48No data—
Fri 2 OctLeiden Lammenschans 18:46No data—
Sun 27 SeptLeiden Lammenschans 18:47No data—
Sat 26 SeptLeiden Lammenschans 18:47No data—
Fri 25 SeptLeiden Lammenschans 18:46No data—
Sun 20 SeptLeiden Lammenschans 18:47No data—
Sat 19 SeptLeiden Lammenschans 18:59No data—
Fri 18 SeptLeiden Lammenschans 18:46No data—
Sun 13 SeptLeiden Lammenschans 18:47No data—
Sat 12 SeptLeiden Lammenschans 18:47No data—
Fri 11 SeptLeiden Lammenschans 18:43No data—
Sun 6 SeptLeiden Lammenschans 19:01No data—
Sat 5 SeptLeiden Lammenschans 18:47No data—
Fri 4 SeptLeiden Lammenschans 18:46No data—
Sun 30 AugLeiden Lammenschans 18:47No data—
Sat 29 AugLeiden Lammenschans 18:48No data—