BIZTRAC BETA
Wholesale of clothing and footwear

HEAD NORGE AS

Org. no. 848878162 Limited company (AS) Asker Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK −4.8m
Equity NOK 1.9m
Incorporated 1988
Share capital NOK 6.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,8 mill kr).

HEAD NORGE AS is registered as a limited company in Asker, Akershus with organisation number 848878162. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 1988. Registered share capital is NOK 6.5m, divided into 1500 shares. The company's stated purpose is: “Kjøp og salg av konfeksjonsvarer, sportsutstyr, agenturvirksomhet, deltagelse i annen virksomhet, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK −4.8m in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK −4.8m
Equity
NOK 1.9m
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Who owns HEAD NORGE AS?

HEAD EIENDOM AS
HEAD NORGE AS
NOK 9.1m rev. · NOK −4.8m profit

HEAD NORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEAD NORGE AS own?

HEAD NORGE AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

HEAD NORGE AS er morselskap for 4 datterselskaper:

Frequently asked questions about HEAD NORGE AS

Who owns HEAD NORGE AS?

HEAD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HEAD NORGE AS?

HEAD NORGE AS had revenue of NOK 9.1m in 2024.

Where is HEAD NORGE AS based?

HEAD NORGE AS has its business address in Vollen.

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.