BIZTRAC BETA
Wholesale of motor vehicle parts and accessories

HYPRO CARTEX AS

Org. no. 939385142 Limited company (AS) Nittedal Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 17.4m
Operating profit NOK 1.9m
Equity NOK 5.0m
Incorporated 1986
Employees 5
Share capital NOK 122,000

HYPRO CARTEX AS is registered as a limited company in Nittedal, Akershus with organisation number 939385142. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 1986 and has 5 registered employees. Registered share capital is NOK 122,000, divided into 275 shares. The company's stated purpose is: “Kjøp og salg av bilrekvisita og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.4m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 17.4m
Operating profit
NOK 1.9m
Equity
NOK 5.0m
Est. value
NOK 8.4m

Financial health · 2024

Liquidity
3.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.4%
Good
Equity as a share of total capital

Who owns HYPRO CARTEX AS?

RAYMOND NÆSS HANSEN
HYPRO CARTEX AS
NOK 17.4m rev. · NOK 1.9m profit

HYPRO CARTEX AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HYPRO CARTEX AS own?

HYPRO CARTEX AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HYPRO CARTEX AS

Who owns HYPRO CARTEX AS?

RAYMOND NÆSS HANSEN is the largest registered owner, with 100.0%.

What is the revenue of HYPRO CARTEX AS?

HYPRO CARTEX AS had revenue of NOK 17.4m in 2024.

Who is the general manager of HYPRO CARTEX AS?

Raymond Næss Hansen is registered as general manager of HYPRO CARTEX AS.

Where is HYPRO CARTEX AS based?

HYPRO CARTEX AS has its business address in Hagan.

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.