Train NS 6784 Tiel – Bodegraven

Tiel 22:48 → Bodegraven 23:45 Daily 0 h 57 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November +2 min

Next service: tomorrow 22:48 from Tiel · Mon 9 Nov

Next departure 22:48 tomorrow · Tiel
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 12 full · 2 partial · 13 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

Worst days

  • Wed 7 Oct Max en route +17 min · last fix heading to — +17 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 95% · 18
  • 3–10 min 0% · 0
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 67% W n=3
  • 100% T n=2
  • 100% F n=5
  • 100% S n=1
  • 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
22:48on time +1 min
22:51≈ on time ≈ +1 min
22:59 / 23:00≈ on time ≈ +1 min
23:05≈ on time ≈ +1 min
23:11 / 23:12≈ on time ≈ +2 min
23:15≈ on time ≈ +2 min
23:19≈ on time ≈ +2 min
23:22≈ on time ≈ +2 min
23:25 / 23:26≈ on time ≈ +2 min
23:36 / 23:37≈ on time ≈ +2 min
23:45on 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
Fri 6 Nov— 23:49+2 min+2 min
Thu 5 Nov— 23:49No data—
Wed 4 Nov— 23:440 min+1 min
Tue 3 Nov— 23:47No data—
Mon 2 Nov— 23:49+3 min+3 min
Sun 1 NovWoerden 23:49Partial coverage0 min—
Sat 31 OctUtrecht Vaartsche Rijn 23:36No data—
Fri 30 Oct— 23:460 min—
Thu 29 Oct— 23:470 min—
Wed 28 Oct— 23:46No data—
Tue 27 Oct— 23:460 min—
Mon 26 Oct— 23:47No data—
Sun 25 OctWoerden 23:51No data—
Sat 24 Oct's-Hertogenbosch 23:45No data—
Fri 23 Oct— 23:46+1 min+1 min
Thu 22 Oct— 23:46No data—
Wed 21 Oct— 23:49No data—
Mon 19 Oct— 23:27No data—
Sun 18 OctUtrecht Vaartsche Rijn 23:38+1 min+1 min
Sat 17 OctWoerden 23:53No data—
Fri 16 Oct— 23:460 min—
Thu 15 Oct— 23:50No data—
Wed 14 Oct— 23:460 min—
Tue 13 Oct— 23:47No data—
Mon 12 Oct— 23:460 min—
Sun 11 OctLeiden Lammenschans 00:17Partial coverage0 min—
Sat 10 Oct— 00:090 min—
Fri 9 Oct— 00:080 min—
Thu 8 Oct— 00:080 min—
Wed 7 Oct— 00:26+17 min+17 min