TS Lines
From customs’ record
INMAA1
Import
TS QINGDAO
CSN cut-off
Not known TS Lines 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
The board holds no CSN cut-off from TS Lines for this call yet. 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 customs’ record (ICEGATE’s public VCN enquiry) — not an advisory from TS Lines; read yesterday at 16:22 IST.
- Port
- Chennai
- INMAA1
- Arrival (ETA)
- Sat 10 Oct
- Short link
- /n/FCRRC
- scmtr.io
SCMTR.io read this call from customs’ record — ICEGATE’s public VCN enquiry. Customs publishes no CSN cut-off. It is not TS Lines’s own word. When TS Lines 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’ record of this call
This call is read from it: ICEGATE lists MAA12026091348 (TS QINGDAO) with rotation 1214606 at INMAA1, expected 10/10/2026.
Read yesterday at 16:22 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.