IC 3316 Nivelles – Anvers-Central

View line IC

Nivelles 16:50 → Anvers-Central 18:20 Sat, Sun 1 h 30 min · 10 stops SNCB/NMBS

✓ Today’s run finished

Today, last fix heading to Anvers-Central at 18:21 No data

  1. Nivelles16:50
  2. Bruxelles-Midi17:23
  3. Bruxelles-Central17:31
  4. Vilvorde17:48
  5. Malines17:58
  6. Anvers-Berchem18:15
  7. Anvers-Central18:20
On-time · 30 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 no data
On-time · 90 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)

Last 30 days

Arrival delay at Anvers-Central, 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

No runs with a known final delay yet.

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

StopSched.
16:50
16:59 / 17:08
17:23 / 17:27
17:31 / 17:32
17:36 / 17:40
17:48 / 17:50
17:58 / 18:00
18:10 / 18:11
18:15 / 18:16
18:20

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 3 October 2026.

Recent runs

DateLast stopFinalMax
Sun 25 OctAnvers-Central 18:21No data—
Sat 24 OctAnvers-Central 18:21No data—
Sun 18 OctAnvers-Central 18:22No data—
Sat 17 OctAnvers-Central 18:21No data—
Sun 11 OctAnvers-Central 18:22No data—
Sat 10 OctAnvers-Central 18:22No data—
Sun 4 OctAnvers-Central 18:21No data—