OOCL
From JNPA's report
INNSA1
Import
OOCL SINGAPORE
CSN cut-off
Not known OOCL 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
OOCL 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 24 Oct 2026 — not an advisory from OOCL; read today at 13:26 IST.
- Port
- Nhava Sheva
- INNSA1
- Arrival (ETA)
- Wed 4 Nov
- 03:00 IST
- Short link
- /n/EESY3
- scmtr.io
SCMTR.io read this call from JNPA's daily berthing report for APMT (Gateway Terminals India) of 24 Oct 2026. It is JNPA's report, which names OOCL for the call — not OOCL's own word. When OOCL 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 NSA12026101962 on ICEGATE’s public record for OOCL SINGAPORE, rotation 1216683, at INNSA1, expected 04/11/2026. Check it against your documents.
Found today at 13:26 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.