Train NS 28309 Utrecht Centraal – Utrecht Maliebaan

Utrecht Centraal 11:30 → Utrecht Maliebaan 11:49 Tue, Wed, Thu, Fri, Sat, Sun 0 h 19 min · 3 stops NS (Nederlandse Spoorwegen)

Running now · updated 11:45

Heading to Utrecht Maliebaan No data

Estimated arrival at Utrecht Maliebaan 11:49 · 38 km/h

  1. Utrecht Centraal11:30
  2. Utrecht Overvecht11:35
  3. Utrecht Maliebaan11:49
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 6 full · 11 partial · 11 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 7 full · 12 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Utrecht Maliebaan, 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=1
  • 100% T n=4
  • 100% W n=3
  • 100% T n=3
  • 100% F n=1
  • 100% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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 10Today
11:30on time on time
11:35 / 11:36≈ on time ≈ on time
11:49on time on time

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 NovUtrecht Overvecht 11:44No data—
Thu 5 NovUtrecht Centraal 11:49No data—
Wed 4 NovUtrecht Overvecht 11:49Partial coverage0 min—
Tue 3 NovUtrecht Overvecht 11:490 min—
Sun 1 NovUtrecht Overvecht 11:520 min—
Sat 31 OctUtrecht Centraal 11:50Partial coverage0 min—
Fri 30 OctUtrecht Centraal 11:50No data—
Thu 29 OctUtrecht Centraal 11:50Partial coverage0 min—
Wed 28 OctUtrecht Centraal 11:51Partial coverage0 min—
Tue 27 OctUtrecht Centraal 11:510 min—
Sun 25 OctUtrecht Centraal 11:50No data—
Sat 24 OctUtrecht Centraal 11:50Partial coverage0 min—
Fri 23 OctUtrecht Centraal 11:50No data—
Thu 22 OctUtrecht Centraal 11:50Partial coverage0 min—
Wed 21 OctUtrecht Centraal 11:50No data—
Tue 20 OctUtrecht Overvecht 11:500 min—
Mon 19 OctUtrecht Centraal 11:50Partial coverage0 min—
Sun 18 OctUtrecht Overvecht 11:540 min—
Sat 17 OctUtrecht Centraal 11:540 min—
Fri 16 OctUtrecht Centraal 11:50No data—
Thu 15 OctUtrecht Overvecht 11:50No data—
Wed 14 OctUtrecht Overvecht 11:51No data—
Tue 13 OctUtrecht Centraal 11:50No data—
Mon 12 OctUtrecht Centraal 11:51No data—
Sun 11 OctUtrecht Centraal 11:50Partial coverage0 min—
Sat 10 OctUtrecht Centraal 11:50Partial coverage0 min—
Fri 9 OctUtrecht Centraal 11:51Partial coverage0 min—
Thu 8 OctUtrecht Centraal 11:50Partial coverage0 min—
Wed 7 OctUtrecht Centraal 12:00Partial coverage0 min—
Tue 6 OctUtrecht Centraal 11:500 min—