Train NS 6789 Bodegraven – Tiel

Bodegraven 23:46 → Tiel 00:42 Daily 0 h 56 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +3 min

Next service: tomorrow 23:46 from Bodegraven · Mon 9 Nov

Next departure 23:46 tomorrow · Bodegraven
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 16 full · 3 partial · 6 no data
On-time · 90 days
79%
19/24 runs under 3 min
RT coverage: 21 full · 3 partial · 17 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 10 Oct Max en route +5 min · last fix heading to — +5 min
  • Thu 29 Oct Max en route +5 min · last fix heading to — +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Wed 4 Nov Max en route +5 min · last fix heading to — +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 19
  • 3–10 min 21% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 80% T n=5
  • 75% W n=4
  • 50% T n=2
  • 75% F n=4
  • 50% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 24 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
23:46on time on time
23:53≈ on time ≈ on time
00:03 / 00:05≈ on time ≈ +1 min
00:07≈ on time ≈ +1 min
00:10≈ on time ≈ +2 min
00:13 / 00:14≈ on time ≈ +2 min
00:17≈ on time ≈ +2 min
00:23≈ on time ≈ +3 min
00:30 / 00:31≈ on time ≈ +3 min
00:38≈ on time ≈ +4 min
00:42on time +4 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
Fri 6 Nov— 00:49+3 min+3 min
Thu 5 Nov— 00:48No data—
Wed 4 Nov— 00:52+4 min+5 min
Tue 3 Nov— 00:440 min—
Mon 2 Nov— 00:43+1 min—
Sun 1 NovTiel Passewaaij 00:53Partial coverage0 min—
Sat 31 Oct— 00:500 min—
Thu 29 Oct— 00:54+5 min+5 min
Wed 28 Oct— 00:430 min—
Tue 27 Oct— 00:480 min—
Mon 26 Oct— 00:450 min—
Sun 25 OctTiel Passewaaij 00:56Partial coverage0 min—
Sat 24 Oct— 00:58No data—
Fri 23 Oct— 01:03+3 min+3 min
Thu 22 Oct— 00:48No data—
Wed 21 Oct— 00:43No data—
Tue 20 Oct— 00:440 min—
Sat 17 OctTiel Passewaaij 00:54No data—
Fri 16 Oct— 00:430 min—
Thu 15 Oct— 00:52No data—
Wed 14 Oct— 00:550 min—
Tue 13 Oct— 00:440 min—
Mon 12 Oct— 00:46+1 min—
Sun 11 OctTiel Passewaaij 00:57Partial coverage0 min—
Sat 10 Oct— 00:56+5 min+5 min
Fri 9 Oct— 00:430 min—
Thu 8 Oct— 00:420 min—
Wed 7 Oct— 00:430 min—
Tue 6 Oct— 00:51+4 min+4 min
Mon 5 OctLeiden Centraal 01:060 min+6 min