Key Facts
493000 at a Glance
Code 493000
Official title Transport via pipeline
Version NIC 2025
Source authority MoSPI
Section H - Transportation and storage
Lg
NIC 2025 MoSPI source NIC 493000 - Transport via pipeline
NIC 493000 classifies transport via pipeline as a final six-digit transport or logistics activity under Section H and Division 49. Use it when this activity is the main source of revenue.
Source Verification for 493000
10 / 10
4 of 4 factors passing
- Verified in official source - Found in NIC_2025.xlsx official MoSPI release dataset.
- International crosswalk available - No official ISIC/NACE/CPC/ISCO correspondence table is bundled in this build input set.
- Migration from previous edition - Legacy migration candidates present from NIC 2008: 1.
- Complete hierarchy chain - All parent levels exist: Section > Division > Group > Class > Sub-class (5 levels).
- Official size/threshold documented - No official code-level size or threshold dataset is included in this source bundle.
- Trade or export crosswalk match - No official NIC-to-HS/export correspondence table is bundled in this source bundle.
- Legacy national crosswalk - Legacy link exists via NIC 2008 converter layer (1 linked legacy codes).
NIC 2008 -> NIC 2025 Mapping for 493000
NIC 2008 links are discovery matches from the local converter layer. Verify final migration decisions against official source documents.
Practical Summary
What Transport via pipeline Means Under NIC 2025
NIC 493000 is the final six-digit endpoint for Transport via pipeline. It should be selected only when the enterprise's primary transport or logistics activity matches this title more closely than nearby sibling codes in the same parent category.
How To Choose
When to Choose 493000 Over Nearby Codes
Choose 493000 only when operations, invoices and revenue narrative align with Transport via pipeline. If the activity also includes nearby sibling codes in the same parent category, compare those pages before filing.
Common Questions About NIC 493000
Does NIC 493000 cover transport itself or logistics support?
Transport codes apply when the business carries passengers or freight. Warehousing, freight forwarding, cargo handling and support activities may sit under different logistics support codes.
What if the business stores goods and also moves them?
Choose the code matching the dominant paid service. A transporter, warehouse operator and freight forwarder can belong to different Sub-classes even when they serve the same supply chain.
How do I verify that NIC 493000 is correct before filing?
Check the parent hierarchy, compare nearby sibling codes in the same parent category, and confirm that the official title matches the main revenue activity. For regulated or filing-critical decisions, verify the source row in the MoSPI dataset.
What happens if I use the wrong NIC code in Udyam or MCA registration?
A wrong code can cause mismatched business descriptions, follow-up questions or later compliance cleanup. It is better to compare nearby codes before filing than to correct a weak classification later.
Is there a legacy NIC 2008 equivalent for NIC 493000?
Use the legacy converter only as a migration aid. Old NIC 2008 matches can suggest where to look, but NIC 2025 should remain the primary reference for new code selection.
NIC 2026 guidance
Before you select NIC 493000
NIC 493000 should be selected only when the official title matches the main revenue-generating activity. If the business also trades, transports, processes, installs or supports the same product or service, compare nearby NIC pages before filing. This reduces the risk of choosing a code that describes the product being handled rather than the activity your enterprise actually performs.
Data Source and Verification Date
Source layer
Official NIC 2025 Excel and PDF from MoSPI.
Last verified
2026-04-21 from the generated NIC 2025 source layer used in this build.
Disclaimer
This is an independent reference tool. Verify filing-critical decisions in official sources.