Train NS 6777 Bodegraven – Tiel

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

✓ Today’s run finished

Today, last fix heading to — at 21:44 +1 min

  1. Bodegraven20:46
  2. Utrecht Centraal21:03
  3. Utrecht Vaartsche Rijn21:07
  4. Houten21:13
  5. Culemborg21:23
  6. Geldermalsen21:30
  7. Tiel21:42

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

Next departure 20:46 Monday · Bodegraven
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 14 full · 2 partial · 12 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 17 full · 2 partial · 29 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 Tiel, 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

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

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

On-time by weekday

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