BIZTRAC BETA
Development of building projects

NP EIENDOM AS

Org. no. 925921688 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −20,000
Equity NOK −824,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−824k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).

NP EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 925921688. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg, utleie og utvikling av eiendom samt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −20,000
Equity
NOK −824,000

Financial health · 2025

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

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

Who owns NP EIENDOM AS?

HØVIKEN AS
NP EIENDOM AS
· NOK −20,000 profit

NP EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NP EIENDOM AS own?

NP EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NP EIENDOM AS

Who owns NP EIENDOM AS?

HØVIKEN AS is the largest registered owner, with 100.0%.

Who is the general manager of NP EIENDOM AS?

Roy Themte is registered as general manager of NP EIENDOM AS.

Where is NP EIENDOM AS based?

NP EIENDOM AS has its business address in Lysaker.

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.