Hapag-Lloyd
From JNPA's report
INNSA1
Import
WADI DUKA
CSN cut-off
Not known Hapag-Lloyd has not published a CSN cut-off for this call that SCMTR.io has found.
What to doIndicative
File early — ask the line
Last foreign port − 72 h · Hapag-Lloyd’s rule
Hapag-Lloyd asks for CSN details at least 72 hours before the ship sails from its last foreign port for India (its India notice of 17 April 2025 — the latest with a deadline we found). No list gives when it sails, so the board shows no date. Ask the line for the ship’s last port and when it sails.
In the line’s words: “Submit all IGM/SCMTR relevant information, House Bill of Lading (HBL) or Cargo Summary Notification (CSN) preferred Container Freight Station (CFS) details etc. to Hapag-Lloyd at least 72 hours prior to vessel sailing from last port of call before calling Indian ports.” Read it
Indicative only — confirm the cut-off with the shipping line. SCMTR.io accepts no liability for a missed cut-off.
Read by SCMTR.io from JNPA's daily berthing report for NSIGT (DP World) of 23 Oct 2026 — not an advisory from Hapag-Lloyd; read today at 13:24 IST.
- Port
- Nhava Sheva
- INNSA1
- Arrival (ETA)
- Sat 31 Oct
- 13:00 IST
- Short link
- /n/Q9EGF
- scmtr.io
SCMTR.io read this call from JNPA's daily berthing report for NSIGT (DP World) of 23 Oct 2026. It is JNPA's report, which names Hapag-Lloyd for the call — not Hapag-Lloyd's own word. When Hapag-Lloyd publishes this call itself, its word replaces this at the same address.
For your CSN
The customs VCN is the one your CSN carries; the port VCN and VIA are the port’s own references.
Customs’ VCN found by the ship’s name
The list names no VCN. SCMTR.io found NSA12026102059 on ICEGATE’s public record for WADI DUKA, rotation 1218200, at INNSA1, expected 31/10/2026. Check it against your documents.
Found today at 11:41 IST. See the call in VCN search
From SCMTR.io
SCMTR filing, checked before ICEGATE sees it
CSN, SAM / SDM and export SCX for forwarders, consol agents and shipping lines — every check before you sign.
- Check your SCMTR JSONFree, no sign-in — what customs would reject, and the fix.
- Track a B/LFree, no login — the SAM status straight from ICEGATE.