BIZTRAC BETA
Manufacture of wooden containers

NORPAX AS

Org. no. 991404090 Limited company (AS) Asker Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 330,000
Equity NOK 1.8m
Incorporated 2007
Share capital NOK 100,000

NORPAX AS is registered as a limited company in Asker, Akershus with organisation number 991404090. The business is classified under manufacture of wooden containers (NACE 16.240). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester til næringslivet, asbestsanering, samt ved aksjer eller på annen måte delta i andre virksomheter som naturlig har tilknytning til virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 330,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 330,000
Equity
NOK 1.8m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.4%
Good
Equity as a share of total capital

Who owns NORPAX AS?

PER HERLOF SELLÆG
NORPAX AS
NOK 5.6m rev. · NOK 330,000 profit

NORPAX AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORPAX AS own?

NORPAX AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

NORPAX AS er morselskap for 1 datterselskap:

Frequently asked questions about NORPAX AS

Who owns NORPAX AS?

PER HERLOF SELLÆG is the largest registered owner, with 100.0%.

What is the revenue of NORPAX AS?

NORPAX AS had revenue of NOK 5.6m in 2024.

Who is the general manager of NORPAX AS?

Per Herlof Sellæg is registered as general manager of NORPAX AS.

Where is NORPAX AS based?

NORPAX AS has its business address in Slemmestad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.