Train NS 6741 Bodegraven – Tiel

Bodegraven 11:46 → Tiel 12:42 Fri, Sat, Sun 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tiel Passewaaij at 12:53 0 min

  1. Bodegraven11:46
  2. Utrecht Centraal12:03
  3. Utrecht Vaartsche Rijn12:07
  4. Houten12:13
  5. Culemborg12:23
  6. Tiel Passewaaij12:38
  7. Tiel12:42

Next service: tomorrow 11:46 from Bodegraven · Sun 15 Nov

Next departure 11:46 tomorrow · Bodegraven
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 5 full · 4 partial · 3 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 9 full · 4 partial · 22 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 Tiel, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +5 min · last fix heading to Tiel Passewaaij +5 min

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 92% · 12
  • 3–10 min 8% · 1
  • 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
  • 75% F n=4
  • 100% S n=5
  • 100% S n=3

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
11:46on time on time
11:53≈ on time ≈ on time
12:03 / 12:05≈ on time ≈ +1 min
12:07≈ on time ≈ +1 min
12:10≈ on time ≈ +1 min
12:13 / 12:14≈ on time ≈ +1 min
12:17≈ on time ≈ +1 min
12:23≈ on time ≈ +1 min
12:30 / 12:31≈ on time ≈ +2 min
12:38≈ on time ≈ +2 min
12:42on 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
Sat 14 NovTiel Passewaaij 12:53Partial coverage0 min—
Fri 13 NovTiel Passewaaij 12:530 min—
Fri 6 NovTiel Passewaaij 12:53No data—
Sun 1 NovTiel Passewaaij 12:54Partial coverage+1 min—
Sat 31 OctTiel Passewaaij 12:54Partial coverage+1 min—
Fri 30 OctTiel Passewaaij 12:530 min—
Sun 25 OctTiel Passewaaij 12:56No data—
Sat 24 OctZaltbommel 13:03+1 min+1 min
Fri 23 OctZaltbommel 13:020 min—
Sun 18 OctTiel Passewaaij 12:530 min—
Sat 17 OctTiel Passewaaij 12:53Partial coverage0 min—
Fri 16 OctTiel Passewaaij 12:53No data—
Sun 11 OctTiel Passewaaij 12:530 min—
Sat 10 OctTiel Passewaaij 12:53+1 min—
Fri 9 OctTiel Passewaaij 12:57+5 min+5 min
Mon 5 OctTiel Passewaaij 12:530 min—
Sun 4 OctTiel Passewaaij 12:52No data—
Sat 3 OctTiel Passewaaij 12:55No data—
Fri 2 OctTiel Passewaaij 12:54No data—
Sun 27 SeptTiel Passewaaij 12:53No data—
Sat 26 SeptTiel Passewaaij 12:53No data—
Fri 25 SeptTiel Passewaaij 12:53No data—
Sun 20 SeptTiel Passewaaij 12:53No data—
Sat 19 SeptTiel Passewaaij 12:53No data—
Fri 18 SeptTiel Passewaaij 12:53No data—
Sun 13 SeptTiel Passewaaij 12:52No data—
Sat 12 SeptTiel Passewaaij 12:53No data—
Fri 11 SeptTiel Passewaaij 12:55No data—
Sun 6 SeptTiel Passewaaij 12:54No data—
Sat 5 SeptTiel Passewaaij 12:56No data—