BIZTRAC BETA
Construction of residential and non-residential buildings

HOVEDLAGERET AS

Org. no. 913691822 Limited company (AS) Ullensvang Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 606,000
Equity NOK 10.3m
Incorporated 2014
Share capital NOK 2.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HOVEDLAGERET AS is registered as a limited company in Ullensvang, Vestland with organisation number 913691822. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 2.1m, divided into 1000 shares. The company's stated purpose is: “Eie og drifte eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 606,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 606,000
Equity
NOK 10.3m
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.2%
Very good
Equity as a share of total capital

Who owns HOVEDLAGERET AS?

Høyer Odda AS
HOVEDLAGERET AS
NOK 2.1m rev. · NOK 606,000 profit

HOVEDLAGERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVEDLAGERET AS

Who owns HOVEDLAGERET AS?

Høyer Odda AS is the largest registered owner, with 100.0%.

What is the revenue of HOVEDLAGERET AS?

HOVEDLAGERET AS had revenue of NOK 2.1m in 2024.

Who is the general manager of HOVEDLAGERET AS?

Arve Kvåle is registered as general manager of HOVEDLAGERET AS.

Where is HOVEDLAGERET AS based?

HOVEDLAGERET AS has its business address in Odda.

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.