Train NS 6781 Bodegraven – Tiel

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

It does not run today

Last recorded run: Friday 6 November +1 min

Next service: Monday 21:46 from Bodegraven · Mon 9 Nov

Next departure 21:46 Monday · Bodegraven
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 13 full · 2 partial · 13 no data
On-time · 90 days
79%
15/19 runs under 3 min
RT coverage: 17 full · 2 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 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

  • Wed 7 Oct Max en route +10 min · last fix heading to — +10 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +5 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Utrecht Centraal +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 15
  • 3–10 min 21% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 67% W n=3
  • 67% T n=3
  • 80% F n=5
  • 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, 19 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
21:46on time on time
21:53≈ on time ≈ +1 min
22:03 / 22:05≈ on time ≈ +2 min
22:07≈ on time ≈ +2 min
22:10≈ on time ≈ +2 min
22:13 / 22:14≈ on time ≈ +2 min
22:17≈ +1 min ≈ +2 min
22:23≈ +1 min ≈ +3 min
22:30 / 22:31≈ +1 min ≈ +4 min
22:38≈ +1 min ≈ +4 min
22:42+1 min +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— 22:44+1 min—
Thu 5 Nov— 22:440 min—
Wed 4 Nov— 22:430 min—
Tue 3 Nov— 22:48No data—
Sun 1 NovTiel Passewaaij 22:53Partial coverage+1 min—
Sat 31 OctTiel Passewaaij 22:52No data—
Fri 30 Oct— 22:430 min—
Thu 29 Oct— 22:43+4 min+4 min
Wed 28 Oct— 22:43No data—
Tue 27 Oct— 22:44No data—
Mon 26 Oct— 22:43No data—
Sun 25 OctTiel Passewaaij 22:53No data—
Sat 24 OctCulemborg 23:00No data—
Fri 23 Oct— 22:590 min—
Thu 22 Oct— 22:46No data—
Wed 21 Oct— 22:46No data—
Tue 20 Oct— 22:43No data—
Mon 19 Oct— 22:44No data—
Sun 18 OctTiel Passewaaij 22:54+2 min+2 min
Sat 17 OctTiel Passewaaij 22:57Partial coverage0 min—
Fri 16 Oct— 22:45+2 min+2 min
Thu 15 Oct— 22:43No data—
Wed 14 Oct— 22:45+2 min+2 min
Tue 13 Oct— 22:45No data—
Mon 12 Oct— 22:450 min—
Sun 11 OctTiel Passewaaij 22:53+1 min—
Sat 10 OctUtrecht Centraal 22:46+3 min+5 min
Fri 9 Oct— 22:48+5 min+6 min
Thu 8 Oct— 22:44+1 min—
Wed 7 Oct— 22:56+10 min+10 min