BIZTRAC BETA
Development of building projects

DANEBU EIENDOMSUTVIKLING AS

Org. no. 929591356 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −54,000
Equity NOK −2.7m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

DANEBU EIENDOMSUTVIKLING AS is registered as a limited company in Larvik, Vestfold with organisation number 929591356. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og utvikle fast eiendom på Danebu i Larvik.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −54,000
Equity
NOK −2.7m

Financial health · 2024

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DANEBU EIENDOMSUTVIKLING AS?

BRUNLANES NÆRING AS
DANEBU EIENDOMSUTVIKLING AS
NOK 0 rev. · NOK −54,000 profit

DANEBU EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DANEBU EIENDOMSUTVIKLING AS

Who owns DANEBU EIENDOMSUTVIKLING AS?

BRUNLANES NÆRING AS is the largest registered owner, with 70.0%.

What is the revenue of DANEBU EIENDOMSUTVIKLING AS?

DANEBU EIENDOMSUTVIKLING AS had revenue of NOK 0 in 2024.

Where is DANEBU EIENDOMSUTVIKLING AS based?

DANEBU EIENDOMSUTVIKLING 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.