Train NS 6742 Tiel – Bodegraven

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

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: Friday 12:18 from Tiel · Fri 20 Nov

Next departure 12:18 Friday · Tiel
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 1 full · 5 partial · 4 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 6 full · 7 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: +3 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

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

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

Stops and timetable

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

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