Wan Hai
From JNPA's report
INNSA1
Import
WAN HAI 312
CSN cut-off
Not known Wan Hai has not published a CSN cut-off for this call that SCMTR.io has found.
What to doIndicative
File early — ask the line
Before last foreign port · Customs’ rule
Wan Hai has not given a CSN cut-off for this call. Customs wants the CSN before the ship leaves its last foreign port for India, and the line’s own arrival manifest (SAM) is due by the same point. No list gives when it sails, so the board shows no date. Ask the line for its CSN cut-off for this call.
Customs’ words: “before departure from the last port of call” — CBIC’s SCMTR table of who files what and when, and ICEGATE’s SCMTR FAQ. 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 APMT (Gateway Terminals India) of 14 Oct 2026 — not an advisory from Wan Hai; read today at 11:44 IST.
- Port
- Nhava Sheva
- INNSA1
- Arrival (ETA)
- Fri 23 Oct
- 08:00 IST
- Short link
- /n/HW79Y
- scmtr.io
SCMTR.io read this call from JNPA's daily berthing report for APMT (Gateway Terminals India) of 14 Oct 2026. It is JNPA's report, which names Wan Hai for the call — not Wan Hai's own word. When Wan Hai 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’ record agrees
ICEGATE lists NSA12026101978 (WAN HAI 312) with rotation 1216801 at INNSA1, expected 23/10/2026.
Checked today at 11:44 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.