LDB Coverage Across Ports, ICDs and CFSs: Choosing the Right Container-Tracking Evidence
By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026
2-minute summary
- LDB has broad but node-specific coverage; the evidence chosen for a shipment should match its actual route through port, terminal, ICD/CFS, rail/road and border nodes.
- The August 2026 official release lists 19 ports, 32 container terminals, 103 ICDs, 439 CFSs/related nodes, 5,569 railway stations, 269 toll plazas and three Integrated Check Posts, among other coverage.
- A missing LDB event may mean the route used a node or mode outside the expected event chain, not necessarily that the container did not move.
Current position
The official 2026 coverage statement spans ports, terminals, ICDs, CFSs, rail stations, toll plazas, SEZs and border nodes. Because event types differ by mode and location, a shipment evidence plan should begin with the expected route rather than assuming every movement generates the same trace.
Control and evidence map
| # | Control / evidence requirement | |
|---|---|---|
| 1 | Map the expected route and mark which LDB-covered nodes should generate observable events. | |
| 2 | For port shipments, distinguish port authority, container terminal and CFS/ICD events. | |
| 3 | For inland movement, identify whether rail FNR, vehicle/FASTag or container RFID evidence is expected. | |
| 4 | If an event is absent, check identifier, mode change and node coverage before escalating. | |
| 5 | Archive a route evidence map for material disputes or high-value customer shipments. | |
Worked example
A container moves from a port to an inland depot by rail, but the team expects highway toll events and flags a false exception. A route-aware evidence map would instead look for rail/FNR and ICD events.
Common mistakes
- Assuming every covered node produces the same event type.
- Confusing a port with a specific terminal.
- Expecting truck toll events on a rail leg.
- Treating a missing event as proof of non-movement without checking identifiers and route.
Frequently asked questions
How broad is LDB coverage?
The 2026 official release describes nationwide EXIM coverage across ports, terminals and extensive inland nodes.
Why map the route first?
Because the expected evidence depends on mode and node.
Can coverage change?
Yes. Use the live LDB coverage page for current operations.
What if a shipment changes mode?
Update the expected event chain and preserve the change reason.
Official sources
- Press Information Bureau / Ministry of Commerce & Industry - Logistics Data Bank Tracks 10 Crore EXIM Containers, Provides Visibility across Logistics Chain (PIB PRID 2299348; 2026-08-14)
- NICDC Logistics Data Services Limited - Logistics Data Bank 2.0 portal, coverage and analytics (Current portal; current)
- NICDC Logistics Data Services Limited - LDB 2.0 Portal User Guide (LDB2.0 Manual; 2025-11)
Disclaimer
Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.