Train NS 6782 Tiel – Bodegraven

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

It does not run today

Last recorded run: Friday 6 November +4 min

Next service: Monday 22:18 from Tiel · Mon 9 Nov

Next departure 22:18 Monday · Tiel
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 12 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 28 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 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

  • Fri 6 Nov Max en route +4 min · last fix heading to — +4 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 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 80% F n=5
  • 100% 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
22:18on time on time
22:21≈ on time ≈ on time
22:29 / 22:30≈ on time ≈ on time
22:35≈ on time ≈ +1 min
22:41 / 22:42≈ on time ≈ +1 min
22:45≈ on time ≈ +1 min
22:49≈ on time ≈ +1 min
22:52≈ on time ≈ +1 min
22:55 / 22:56≈ on time ≈ +1 min
23:06 / 23:07≈ on time ≈ +1 min
23:15on time +1 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:23+4 min+4 min
Thu 5 Nov— 23:19No data—
Wed 4 Nov— 23:140 min+1 min
Tue 3 Nov— 23:15No data—
Mon 2 Nov— 23:17+1 min+1 min
Sun 1 NovWoerden 23:190 min—
Sat 31 OctWoerden 23:21No data—
Fri 30 Oct— 23:250 min—
Thu 29 Oct— 23:160 min+1 min
Wed 28 Oct— 23:16No data—
Mon 26 Oct— 23:16No data—
Sun 25 OctWoerden 23:21No data—
Sat 24 OctHouten 23:150 min—
Fri 23 Oct— 23:160 min—
Thu 22 Oct— 23:17No data—
Wed 21 Oct— 23:16No data—
Tue 20 Oct— 23:160 min—
Mon 19 Oct— 22:56No data—
Sun 18 OctUtrecht Vaartsche Rijn 23:060 min—
Sat 17 OctWoerden 23:21No data—
Fri 16 Oct— 23:18+1 min+2 min
Thu 15 Oct— 23:45No data—
Wed 14 Oct— 23:170 min—
Tue 13 Oct— 23:18No data—
Mon 12 Oct— 23:170 min—
Sun 11 OctLeiden Lammenschans 23:49+2 min+2 min
Sat 10 Oct— 23:390 min—
Fri 9 Oct— 23:380 min—
Thu 8 Oct— 23:380 min—
Wed 7 Oct— 23:380 min—