COSCO
From JNPA's report
INNSA1
Import
ADVANCE
CSN cut-off
Not known COSCO 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
COSCO 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 BMCT (PSA Mumbai) of 8 Oct 2026 — not an advisory from COSCO; read yesterday at 16:16 IST.
- Port
- Nhava Sheva
- INNSA1
- Arrival (ETA)
- Wed 14 Oct
- 12:30 IST
- Short link
- /n/CSERX
- scmtr.io
SCMTR.io read this call from JNPA's daily berthing report for BMCT (PSA Mumbai) of 8 Oct 2026. It is JNPA's report, which names COSCO for the call — not COSCO's own word. When COSCO publishes this call itself, its word replaces this at the same address.
For your CSN
No customs VCN yet
Customs usually lists a call a few days before it arrives. SCMTR.io asks ICEGATE every few hours and adds the VCN here when it does — last asked yesterday at 21:04 IST.
More calls of “ADVANCE”?
Ask ICEGATE’s public vessel record for every call of this ship, with its VCN.
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.