Train NS 6743 Woerden – Tiel

Woerden 12:23 → Tiel 13:12 Fri, Sat, Sun 0 h 49 min · 10 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Tiel Passewaaij at 13:28 +5 min

  1. Woerden12:23
  2. Utrecht Vaartsche Rijn12:37
  3. Utrecht Lunetten12:40
  4. Houten Castellum12:47
  5. Culemborg12:53
  6. Tiel Passewaaij13:08
  7. Tiel13:12

Next service: tomorrow 12:23 from Woerden · Sat 21 Nov

Next departure 12:23 tomorrow · Woerden
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 5 full · 3 partial · 3 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Fri 20 Nov Max en route +6 min · last fix heading to Tiel Passewaaij +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
12:23on time on time
12:33 / 12:35≈ on time ≈ on time
12:37≈ on time ≈ +1 min
12:40≈ on time ≈ +1 min
12:43 / 12:44≈ on time ≈ +1 min
12:47≈ on time ≈ +1 min
12:53≈ on time ≈ +1 min
13:00 / 13:01≈ +1 min ≈ +1 min
13:08≈ +1 min ≈ +2 min
13:12+1 min +2 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 20 NovTiel Passewaaij 13:28Partial coverage+5 min+6 min
Sun 15 NovTiel Passewaaij 13:230 min—
Sat 14 NovTiel Passewaaij 13:230 min—
Fri 13 NovTiel Passewaaij 13:23Partial coverage+2 min+2 min
Fri 6 NovTiel Passewaaij 13:23No data—
Sun 1 NovTiel Passewaaij 13:24+1 min—
Sat 31 OctTiel Passewaaij 13:230 min—
Fri 30 OctTiel Passewaaij 13:25Partial coverage0 min—
Sun 25 OctTiel Passewaaij 13:23No data—
Sat 24 OctZaltbommel 13:33+1 min+1 min
Fri 23 OctZaltbommel 13:32No data—
Sun 18 OctTiel Passewaaij 13:23+1 min—
Sat 17 OctTiel Passewaaij 13:230 min—
Fri 16 OctTiel Passewaaij 13:23Partial coverage0 min—
Sun 11 OctTiel Passewaaij 13:24+2 min+2 min
Sat 10 OctTiel Passewaaij 13:230 min—
Fri 9 OctTiel Passewaaij 13:23+1 min—
Mon 5 OctTiel Passewaaij 13:25+2 min+2 min
Sun 4 OctTiel Passewaaij 13:24No data—
Sat 3 OctTiel Passewaaij 13:26No data—
Fri 2 OctTiel Passewaaij 13:23No data—
Sun 27 SeptTiel Passewaaij 13:23No data—
Sat 26 SeptTiel Passewaaij 13:24No data—
Fri 25 SeptTiel Passewaaij 13:23No data—
Sun 20 SeptTiel Passewaaij 13:23No data—
Sat 19 SeptTiel Passewaaij 13:26No data—
Fri 18 SeptTiel Passewaaij 13:22No data—
Sun 13 SeptTiel Passewaaij 13:24No data—
Sat 12 SeptTiel Passewaaij 13:25No data—
Fri 11 SeptTiel Passewaaij 13:23No data—