Train NS 28321 Utrecht Centraal – Utrecht Maliebaan

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

✓ Today’s run finished

Today, last fix heading to Utrecht Centraal at 14:49 0 min

  1. Utrecht Centraal14:30
  2. Utrecht Overvecht14:35
  3. Utrecht Maliebaan14:49

Next service: tomorrow 14:30 from Utrecht Centraal · Thu 19 Nov

Next departure 14:30 tomorrow · Utrecht Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 0 full · 19 partial · 7 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 1 full · 26 partial · 52 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

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

  • Early 0% · 0
  • On time 100% · 27
  • 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=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=2
  • 100% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 27 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
14:30on time on time
14:35 / 14:36— —
14:49— —

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