Skip to content
SCMTR

GFS

From JNPA's report

INNSA1

Import

GFS GENESIS

CSN cut-off

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

What to doIndicative

File now — ask the line

Before last foreign port · Customs’ rule

GFS 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. The ship is due within three days, so its last foreign port is probably behind it — ask the line now.

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 GFS; read yesterday at 16:12 IST.

Port
Nhava Sheva
INNSA1
Arrival (ETA)
Sat 10 Oct
15:00 IST
Short link
/n/C8YSB
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 GFS for the call — not GFS's own word. When GFS publishes this call itself, its word replaces this at the same address.

Open JNPA’s page

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. VIA S1704 falls between NSA12026091703 and NSA12026091708, which ICEGATE does list, so it was issued that month too.

ICEGATE has not listed this call yet (asked yesterday at 16:12 IST); SCMTR.io asks again every few hours and replaces this with customs’ own VCN when it does. Check it before you file.

More calls of “GFS GENESIS”?

Ask ICEGATE’s public vessel record for every call of this ship, with its VCN.

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 GFS before you rely on it — and if you are GFS, 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