Train NS 6776 Tiel – Bodegraven

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 20:48 from Tiel · Fri 6 Nov

Next departure 20:48 today · Tiel
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 12 full · 1 partial · 13 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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