Train NS 6770 Tiel – Bodegraven

Tiel 19:18 → Bodegraven 20:15 Fri, Sat, Sun 0 h 57 min · 11 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November 0 min

Next service: Friday 19:18 from Tiel · Fri 13 Nov

Next departure 19:18 Friday · Tiel
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 7 full · 3 partial · 2 no data
On-time · 90 days
91%
10/11 runs under 3 min
RT coverage: 8 full · 3 partial · 22 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

  • Mon 5 Oct Max en route +12 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 10
  • 3–10 min 0% · 0
  • 10–30 min 9% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 11 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
19:18on time on time
19:21≈ on time ≈ on time
19:29 / 19:30≈ on time ≈ +1 min
19:35≈ on time ≈ +1 min
19:41 / 19:42≈ on time ≈ +2 min
19:45≈ on time ≈ +2 min
19:49≈ on time ≈ +2 min
19:52≈ on time ≈ +2 min
19:55 / 19:56≈ on time ≈ +3 min
20:06 / 20:07≈ on time ≈ +3 min
20:15on time +4 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— 20:140 min—
Sun 1 NovWoerden 20:19Partial coverage0 min—
Sat 31 OctWoerden 20:21Partial coverage0 min—
Sun 25 OctWoerden 20:21No data—
Sat 24 OctWoerden 20:190 min—
Fri 23 OctGeldermalsen 20:16+1 min+1 min
Sun 18 OctUtrecht Vaartsche Rijn 20:060 min—
Sat 17 OctWoerden 20:21Partial coverage0 min—
Fri 16 OctUtrecht Vaartsche Rijn 20:16No data—
Sun 11 OctLeiden Lammenschans 20:470 min—
Sat 10 OctLeiden Lammenschans 20:470 min—
Fri 9 Oct— 20:38+1 min—
Mon 5 Oct— 20:50+11 min+12 min
Sun 4 OctLeiden Lammenschans 20:47No data—
Sat 3 OctLeiden Lammenschans 20:51No data—
Sun 27 SeptLeiden Lammenschans 21:01No data—
Sat 26 SeptLeiden Lammenschans 20:56No data—
Sun 20 SeptLeiden Lammenschans 20:49No data—
Sat 19 SeptLeiden Lammenschans 20:47No data—
Sun 13 SeptLeiden Lammenschans 20:48No data—
Sat 12 SeptLeiden Lammenschans 21:01No data—
Sun 6 SeptLeiden Lammenschans 20:47No data—
Sat 5 SeptLeiden Lammenschans 20:47No data—
Sun 30 AugLeiden Lammenschans 20:47No data—
Sat 29 AugLeiden Lammenschans 20:47No data—
Fri 28 AugGeldermalsen 19:44No data—
Sun 23 AugUtrecht Vaartsche Rijn 20:22No data—
Sat 22 AugUtrecht Vaartsche Rijn 20:22No data—
Fri 21 AugUtrecht Vaartsche Rijn 20:04No data—
Wed 19 AugTiel Passewaaij 19:40No data—