HMM
From JNPA's report
INNSA1
Import
HMM MANILA
CSN cut-off
Not known HMM 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
HMM 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 4 Nov 2026 — not an advisory from HMM; read today at 13:32 IST.
- Port
- Nhava Sheva
- INNSA1
- Arrival (ETA)
- Wed 11 Nov
- 13:00 IST
- Short link
- /n/TJHPE
- scmtr.io
SCMTR.io read this call from JNPA's daily berthing report for BMCT (PSA Mumbai) of 4 Nov 2026. It is JNPA's report, which names HMM for the call — not HMM's own word. When HMM publishes this call itself, its word replaces this at the same address.
For your CSN
VCN worked out from the VIA — not on ICEGATE yet
At Nhava Sheva the customs VCN is the port, the month the VIA was issued and the VIA’s own number — here, VIA S2139.
ICEGATE has not listed this call yet (asked today at 13:37 IST); SCMTR.io replaces this with customs’ own VCN once it does. Check it before you file.
More calls of “HMM MANILA”?
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.