Train NS 6740 Tiel – Bodegraven

Tiel 11:48 → Bodegraven 12:45 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 11:48 from Tiel · Fri 6 Nov

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

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

  • Early 0% · 0
  • On time 100% · 10
  • 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=2
  • 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, 10 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
11:48on time on time
11:51≈ on time ≈ on time
11:59 / 12:00≈ on time ≈ on time
12:05≈ on time ≈ on time
12:11 / 12:12≈ on time ≈ +1 min
12:15≈ on time ≈ +1 min
12:19≈ on time ≈ +1 min
12:22≈ on time ≈ +1 min
12:25 / 12:26≈ on time ≈ +1 min
12:36 / 12:37≈ on time ≈ +1 min
12:45on 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 12:52Partial coverage0 min—
Sat 31 OctWoerden 12:51Partial coverage0 min—
Fri 30 OctWoerden 12:51No data—
Sun 25 OctWoerden 12:51No data—
Sat 24 OctWoerden 12:480 min—
Fri 23 OctWoerden 12:50No data—
Sun 18 OctUtrecht Vaartsche Rijn 12:360 min—
Sat 17 OctWoerden 12:51Partial coverage0 min—
Fri 16 OctWoerden 12:510 min—
Sun 11 OctLeiden Lammenschans 13:18+1 min+1 min
Sat 10 OctLeiden Lammenschans 13:19+2 min+2 min
Fri 9 OctLeiden Lammenschans 13:17+1 min—
Mon 5 OctLeiden Lammenschans 13:180 min+1 min
Sun 4 OctLeiden Lammenschans 13:17No data—
Sat 3 OctLeiden Lammenschans 13:18No data—
Fri 2 OctLeiden Lammenschans 13:17No data—
Sun 27 SeptLeiden Lammenschans 13:17No data—
Sat 26 SeptLeiden Lammenschans 13:17No data—
Fri 25 SeptLeiden Lammenschans 13:17No data—
Sun 20 SeptLeiden Lammenschans 13:17No data—
Sat 19 SeptLeiden Lammenschans 13:17No data—
Fri 18 SeptLeiden Lammenschans 13:17No data—
Sun 13 SeptLeiden Lammenschans 13:19No data—
Sat 12 SeptLeiden Lammenschans 13:21No data—
Fri 11 SeptLeiden Lammenschans 13:17No data—
Sun 6 SeptLeiden Lammenschans 13:17No data—
Sat 5 SeptLeiden Lammenschans 13:17No data—
Fri 4 SeptLeiden Lammenschans 13:17No data—
Sun 30 AugLeiden Lammenschans 13:18No data—
Sat 29 AugLeiden Lammenschans 13:17No data—