BIZTRAC BETA
Development of building projects

HAVNEPIREN EIENDOMSUTVIKLING AS

Org. no. 992257423 Limited company (AS) Stjørdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6,000
Equity NOK 819,000
Incorporated 2008
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

HAVNEPIREN EIENDOMSUTVIKLING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 992257423. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2008. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drive utleie, utvikling, kjøp og salg av eiendom og alt der tilhørende og relatert samt investering i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 819,000
Est. value
NOK 747,000

Financial health · 2024

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

Who owns HAVNEPIREN EIENDOMSUTVIKLING AS?

PLATON PROSJEKTUTVIKLING AS
HAVNEPIREN EIENDOMSUTVIKLING AS
NOK 0 rev. · NOK −6,000 profit

HAVNEPIREN EIENDOMSUTVIKLING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAVNEPIREN EIENDOMSUTVIKLING AS

Who owns HAVNEPIREN EIENDOMSUTVIKLING AS?

PLATON PROSJEKTUTVIKLING AS is the largest registered owner, with 60.0%.

What is the revenue of HAVNEPIREN EIENDOMSUTVIKLING AS?

HAVNEPIREN EIENDOMSUTVIKLING AS had revenue of NOK 0 in 2024.

Where is HAVNEPIREN EIENDOMSUTVIKLING AS based?

HAVNEPIREN EIENDOMSUTVIKLING AS has its business address in Stjørdal.

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.