Train NS 6788 Tiel – Bodegraven

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 23:48 from Tiel · Mon 16 Nov

Next departure 23:48 today · Tiel
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 5 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 27 full · 3 partial · 14 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: +2 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 13 Nov Max en route +37 min · last fix heading to — +37 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 80% F n=5
  • 100% S n=3
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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
23:48on time on time
23:51≈ on time ≈ on time
23:59 / 00:00≈ on time ≈ on time
00:05≈ on time ≈ on time
00:11 / 00:12≈ on time ≈ +1 min
00:15≈ on time ≈ +1 min
00:19≈ on time ≈ +1 min
00:22≈ on time ≈ +1 min
00:25 / 00:26≈ on time ≈ +1 min
00:36 / 00:37≈ on time ≈ +1 min
00: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
Sun 15 NovWoerden 00:52Partial coverage0 min+1 min
Sat 14 Nov— 00:470 min—
Fri 13 Nov— 01:59+37 min+37 min
Thu 12 Nov— 00:49+1 min+3 min
Wed 11 Nov— 00:490 min+1 min
Tue 10 Nov— 00:440 min—
Mon 9 Nov— 00:440 min—
Fri 6 Nov— 00:49+2 min+3 min
Wed 4 Nov— 00:440 min—
Tue 3 Nov— 00:490 min—
Sun 1 NovWoerden 00:52Partial coverage+1 min+2 min
Sat 31 Oct— 00:490 min—
Fri 30 Oct— 01:13No data—
Wed 28 Oct— 00:46No data—
Tue 27 Oct— 01:110 min—
Mon 26 Oct— 00:500 min—
Sun 25 OctWoerden 01:13No data—
Sat 24 Oct— 00:45No data—
Fri 23 Oct— 00:50+2 min+2 min
Thu 22 Oct— 00:510 min—
Wed 21 Oct— 00:59No data—
Tue 20 Oct— 00:520 min—
Mon 19 Oct— 00:260 min—
Sun 18 OctUtrecht Vaartsche Rijn 00:360 min—
Sat 17 OctWoerden 00:51No data—
Fri 16 Oct— 00:49+1 min+2 min
Thu 15 Oct— 00:550 min—
Wed 14 Oct— 00:550 min—
Tue 13 Oct— 00:51No data—
Mon 12 Oct— 00:460 min—