Train NS 6774 Tiel – Bodegraven

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

It does not run today

Last recorded run: Friday 6 November 0 min

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

Next departure 20:18 Monday · Tiel
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 14 full · 3 partial · 11 no data
On-time · 90 days
95%
20/21 runs under 3 min
RT coverage: 18 full · 3 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

  • Wed 7 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 20
  • 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=2
  • 50% W n=2
  • 100% T n=3
  • 100% F n=5
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 21 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
20:18on time on time
20:21≈ on time ≈ on time
20:29 / 20:30≈ on time ≈ on time
20:35≈ on time ≈ on time
20:41 / 20:42≈ on time ≈ on time
20:45≈ on time ≈ +1 min
20:49≈ on time ≈ +1 min
20:52≈ on time ≈ +1 min
20:55 / 20:56≈ on time ≈ +1 min
21:06 / 21:07≈ on time ≈ +1 min
21: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— 21:140 min—
Thu 5 Nov— 21:190 min—
Wed 4 Nov— 21:140 min—
Tue 3 Nov— 21:14No data—
Sun 1 NovWoerden 21:19Partial coverage0 min—
Sat 31 OctWoerden 21:21Partial coverage0 min—
Fri 30 Oct— 21:190 min—
Thu 29 Oct— 21:16+1 min+1 min
Wed 28 Oct— 21:18No data—
Tue 27 Oct— 21:17No data—
Mon 26 Oct— 21:180 min—
Sun 25 OctWoerden 21:22No data—
Sat 24 OctWoerden 21:18No data—
Fri 23 Oct— 21:16+1 min—
Thu 22 Oct— 21:17No data—
Wed 21 Oct— 21:17No data—
Tue 20 Oct— 21:160 min—
Mon 19 Oct— 20:57No data—
Sun 18 OctUtrecht Vaartsche Rijn 21:060 min—
Sat 17 OctWoerden 21:21Partial coverage0 min—
Fri 16 Oct— 21:150 min—
Thu 15 Oct— 21:19No data—
Wed 14 Oct— 21:16No data—
Tue 13 Oct— 21:23No data—
Mon 12 Oct— 21:170 min—
Sun 11 OctLeiden Lammenschans 21:470 min—
Sat 10 OctLeiden Lammenschans 21:46+1 min+2 min
Fri 9 Oct— 21:380 min—
Thu 8 Oct— 21:410 min+1 min
Wed 7 Oct— 21:49+6 min+6 min