What is NIC 2008 28291?

NIC 2008 28291 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 28291

Manufacture of machinery for making paper pulp, paper, paperboard and articles of paper board

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

282901 - high

Manufacture of machinery for making paper pulp, paper, paperboard and articles of paper board

282902 - medium

Manufacture of machinery for working soft rubber or plastics or for the manufacture of products of these materials

282903 - low

Manufacture of printing and bookbinding machines and machines for activities supporting printing on a variety of materials (other than textiles)

282905 - low

Manufacture of machinery used in the pharmaceutical industry like, tablet pressers, capsule fillers, coating machines, and similar machineries

282906 - low

Manufacture of industrial robots performing multiple tasks for special purposes

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.