BIZTRAC BETA
Activities of agents involved in the wholesale of other particular products

HIMMELHAGEN AS

Org. no. 974465795 Limited company (AS) Lørenskog Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 162,000
Operating profit NOK 45,000
Equity NOK 431,000
Incorporated 1995
Share capital NOK 500,000

HIMMELHAGEN AS is registered as a limited company in Lørenskog, Akershus with organisation number 974465795. The business is classified under activities of agents involved in the wholesale of other particular products (NACE 46.180). The company was incorporated in 1995. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drive med helse, hud- og kroppspleie, samt kjøp og salg av varer i denne forbindelse. Selskapet skal også drive utleie av boliger og delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 162,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2024

Revenue
NOK 162,000
Operating profit
NOK 45,000
Equity
NOK 431,000
Est. value
NOK 349,000

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.1%
Good
Equity as a share of total capital

Who owns HIMMELHAGEN AS?

BJØRN HARLAUGSETER
HIMMELHAGEN AS
NOK 162,000 rev. · NOK 45,000 profit

HIMMELHAGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HIMMELHAGEN AS

Who owns HIMMELHAGEN AS?

BJØRN HARLAUGSETER is the largest registered owner, with 50.0%.

What is the revenue of HIMMELHAGEN AS?

HIMMELHAGEN AS had revenue of NOK 162,000 in 2024.

Who is the general manager of HIMMELHAGEN AS?

Kjerstin Harlaugseter is registered as general manager of HIMMELHAGEN AS.

Where is HIMMELHAGEN AS based?

HIMMELHAGEN AS has its business address in Lørenskog.

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.