BIZTRAC BETA
Buying and selling of own real estate

HVU EIENDOM AS

Org. no. 929208692 Limited company (AS) Horten Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 108,000
Operating profit NOK −97,000
Equity NOK 13.2m
Incorporated 2022
Share capital NOK 8.3m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HVU EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 929208692. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 8.3m, divided into 413 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. ”. The most recent filed accounts, for the 2025 financial year, show NOK 108,000 in revenue and NOK −97,000 in operating profit.

Key figures · 2025

Revenue
NOK 108,000
Operating profit
NOK −97,000
Equity
NOK 13.2m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns HVU EIENDOM AS?

HBP INVEST AS
HVU EIENDOM AS
NOK 108,000 rev. · NOK −97,000 profit

HVU EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HVU EIENDOM AS

Who owns HVU EIENDOM AS?

HBP INVEST AS is the largest registered owner, with 51.6%.

What is the revenue of HVU EIENDOM AS?

HVU EIENDOM AS had revenue of NOK 108,000 in 2025.

Who is the general manager of HVU EIENDOM AS?

Ole William Nærsnes is registered as general manager of HVU EIENDOM AS.

Where is HVU EIENDOM AS based?

HVU EIENDOM AS has its business address in Horten.

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.