What is NIC 2008 26309?

NIC 2008 26309 is an older NIC activity-code reference. This page shows current NIC 2025 candidate pages available in the local converter layer.

Is this a guaranteed one-to-one replacement?

No. The converter layer is a discovery aid. Older NIC codes can be split, merged or restructured, so final use should be verified against the official MoSPI NIC 2025 source.

Where should I go after finding a current candidate?

Open the current NIC 2025 page, review the key facts, hierarchy, similar codes and practical use notes, then verify critical filing decisions in official sources.

Legacy NIC lookup

NIC 2008 26309

Manufacture of other communication equipments n.e.c.

This legacy page points to current NIC 2025 candidates already available in the local converter layer. Treat these matches as discovery aids and verify final use in official MoSPI sources.

Current NIC 2025 candidates

263099 - high

Manufacture of other communication equipments n.e.c. such as pagers, modems, carrier equipment, devices using infrared signals (like remote controllers and game controllers), User Terminals for Broadband Communication, Inflight and Meritime Communication equipments

263006 - medium

Manufacture of radio trans receivers (wireless communication sets)

263007 - medium

Manufacture of telecom transmission equipment such as DWDM, OLT, OFC and SDH.

263008 - medium

Manufacture of telecom mobile technology products including RAN equipment such as base station and antenna

263004 - medium

Manufacture of cable television equipment, transmitting and receiving antenna including DTH dish

Legacy crosswalk hub

Browse the available old-to-current classifier lookup layers.

NIC 2008 converter

Search older NIC 2008 codes and titles across the full local converter layer.

Sources

Review the source files, source notes and limitations behind the generated pages.

Legacy lookup FAQ

Is this old NIC code still the main current standard?

No. The current site layer is NIC 2025. NIC 2008 is retained for historical lookup and migration context.

Why can one old code have multiple current candidates?

Classification revisions can split or merge activity scopes. When the local layer cannot prove a direct one-to-one relation, candidates are shown as migration hints.

Can this page replace official verification?

No. Use it to find likely current pages, then confirm the final code in official MoSPI material before regulated use.