Train NS 6747 Bodegraven – Tiel

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

It does not run today

Last recorded run: Sunday 15 November +1 min

Next service: tomorrow 13:16 from Bodegraven · Fri 20 Nov

Next departure 13:16 tomorrow · Bodegraven
On-time · 30 days
67%
4/6 runs under 3 min
RT coverage: 2 full · 4 partial · 4 no data
On-time · 90 days
77%
10/13 runs under 3 min
RT coverage: 8 full · 5 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 +4 min · last fix heading to Tiel Passewaaij +4 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Zaltbommel +3 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Tiel Passewaaij +3 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 77% · 10
  • 3–10 min 23% · 3
  • 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
  • 67% F n=3
  • 80% S n=5
  • 75% 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
13:16on time on time
13:23≈ on time ≈ on time
13:33 / 13:35≈ on time ≈ +1 min
13:37≈ on time ≈ +1 min
13:40≈ on time ≈ +1 min
13:43 / 13:44≈ on time ≈ +2 min
13:47≈ on time ≈ +2 min
13:53≈ on time ≈ +2 min
14:00 / 14:01≈ on time ≈ +3 min
14:08≈ on time ≈ +3 min
14:12on time +3 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 NovTiel Passewaaij 14:23Partial coverage+1 min—
Sat 14 NovTiel Passewaaij 14:23Partial coverage0 min—
Fri 13 NovTiel Passewaaij 14:220 min—
Fri 6 NovTiel Passewaaij 14:23No data—
Sun 1 NovTiel Passewaaij 14:27Partial coverage+3 min+4 min
Sat 31 OctTiel Passewaaij 14:23Partial coverage+1 min—
Fri 30 OctTiel Passewaaij 14:23No data—
Sun 25 OctTiel Passewaaij 14:24No data—
Sat 24 OctZaltbommel 14:32+3 min+3 min
Fri 23 OctZaltbommel 14:32No data—
Sun 18 OctTiel Passewaaij 14:230 min—
Sat 17 OctTiel Passewaaij 14:23Partial coverage0 min—
Fri 16 OctTiel Passewaaij 14:230 min—
Sun 11 OctTiel Passewaaij 14:230 min—
Sat 10 OctTiel Passewaaij 14:23+1 min—
Fri 9 OctTiel Passewaaij 14:25+4 min+4 min
Mon 5 OctTiel Passewaaij 14:230 min—
Sun 4 OctTiel Passewaaij 14:23No data—
Sat 3 OctTiel Passewaaij 14:23No data—
Fri 2 OctTiel Passewaaij 14:27No data—
Sun 27 SeptTiel Passewaaij 14:22No data—
Sat 26 SeptTiel Passewaaij 14:24No data—
Fri 25 SeptTiel Passewaaij 14:23No data—
Sun 20 SeptTiel Passewaaij 14:23No data—
Sat 19 SeptTiel Passewaaij 14:23No data—
Fri 18 SeptTiel Passewaaij 14:24No data—
Sun 13 SeptTiel Passewaaij 14:22No data—
Sat 12 SeptTiel Passewaaij 14:25No data—
Fri 11 SeptTiel Passewaaij 14:32No data—
Sun 6 SeptTiel Passewaaij 14:23No data—