BIZTRAC BETA
Rental and operating of own or leased real estate

DAMPEJORDET EIENDOM AS

Org. no. 979504764 Limited company (AS) Larvik Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 2.0m
Equity NOK 27.0m
Incorporated 1997
Share capital NOK 19.8m

DAMPEJORDET EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 979504764. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 19.8m, divided into 1980 shares. The company's stated purpose is: “Erverve, forvalte og utvikle fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 2.0m
Equity
NOK 27.0m
Est. value
NOK 24.3m

Financial health · 2024

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

Who owns DAMPEJORDET EIENDOM AS?

NG EIENDOM VESTFOLD TELEMARK AS
DAMPEJORDET EIENDOM AS
NOK 3.4m rev. · NOK 2.0m profit

DAMPEJORDET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DAMPEJORDET EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about DAMPEJORDET EIENDOM AS

Who owns DAMPEJORDET EIENDOM AS?

NG EIENDOM VESTFOLD TELEMARK AS is the largest registered owner, with 100.0%.

What is the revenue of DAMPEJORDET EIENDOM AS?

DAMPEJORDET EIENDOM AS had revenue of NOK 3.4m in 2024.

Who is the general manager of DAMPEJORDET EIENDOM AS?

Torgeir Herlofsen is registered as general manager of DAMPEJORDET EIENDOM AS.

Where is DAMPEJORDET EIENDOM AS based?

DAMPEJORDET EIENDOM AS has its business address in Larvik.

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.