Skip to content
SCMTR

RCL

From JNPA's report

INNSA1

Import

HUNSA BHUM

CSN cut-off

Not known RCL has not published a CSN cut-off for this call that SCMTR.io has found.

What to doIndicative

File early — ask the line

HBL data due: Last foreign port − 72 h · RCL’s rule

RCL asks for house-bill (HBL) data and CFS nominations at least 72 hours before the ship sails from its last foreign port for India (RCL Agencies (India)’s undated client advisory for Nhava Sheva and Mundra, on ODeX (file dated 13 March 2025)). 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: “Customer needs to upload HBL data / CFS nomination requests via ODEX prior 72 hours of the vessel sailing from the last foreign port.” 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 25 Oct 2026 — not an advisory from RCL; read today at 16:22 IST.

Port
Nhava Sheva
INNSA1
Arrival (ETA)
Mon 2 Nov
16:00 IST
Short link
/n/J9MYQ
scmtr.io

SCMTR.io read this call from JNPA's daily berthing report for BMCT (PSA Mumbai) of 25 Oct 2026. It is JNPA's report, which names RCL for the call — not RCL's own word. When RCL publishes this call itself, its word replaces this at the same address.

Open JNPA’s page

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 NSA12026101996 on ICEGATE’s public record for HUNSA BHUM, rotation 1217002, at INNSA1, expected 01/11/2026 — 1 day from the arrival above. Check it against your documents.

Found today at 16:09 IST. See the call in VCN search

Every CSN cut-off on SCMTR.io is indicative, for reference only. Each is copied from a shipping line’s advisory, read from a list a line or a port published, or estimated from a line’s published rule, and any of them may be out of date, misread or changed by the line without notice. The shipping line’s own advisory is the only authority: confirm the cut-off with your line before you rely on it. SCMTR.io accepts no responsibility or liability for a cut-off missed, a CSN filed late, or any charge, amendment or delay that follows.

SCMTR.io reads this from a published list, and does not set or change cut-offs. Confirm with RCL before you rely on it — and if you are RCL, send your own advisory to lines@scmtr.io and it replaces this.

All CSN cut-offs

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.

Everything SCMTR.io does