BIZTRAC BETA
Rental and operating of own or leased real estate

HVAMMEN EIENDOM AS

Org. no. 989188291 Limited company (AS) Kongsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 1.2m
Equity NOK 4.2m
Incorporated 2005
Share capital NOK 133,000

HVAMMEN EIENDOM AS is registered as a limited company in Kongsberg, Buskerud with organisation number 989188291. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 133,000, divided into 242 shares. The company's stated purpose is: “Kjøp, salg og utleie, samt drift av fast eiendom og alt som står i forbindelse med dette. I tillegg omfattes også kjøp, salg og utleie av maskiner og utstyr, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 1.2m
Equity
NOK 4.2m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns HVAMMEN EIENDOM AS?

HVAMMEN HOLDING AS
HVAMMEN EIENDOM AS
NOK 4.1m rev. · NOK 1.2m profit

HVAMMEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HVAMMEN EIENDOM AS

Who owns HVAMMEN EIENDOM AS?

HVAMMEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HVAMMEN EIENDOM AS?

HVAMMEN EIENDOM AS had revenue of NOK 4.1m in 2024.

Who is the general manager of HVAMMEN EIENDOM AS?

Jan Roger Hvammen is registered as general manager of HVAMMEN EIENDOM AS.

Where is HVAMMEN EIENDOM AS based?

HVAMMEN EIENDOM AS has its business address in Kongsberg.

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.