BIZTRAC BETA
Buying and selling of own real estate

HOVED EIENDOM AS

Org. no. 936412564 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −127,000
Equity NOK −91,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−91k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−127k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-03.

HOVED EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 936412564. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å eie, utvikle, forvalte og selge fast eiendom, samt å investere i eiendomsselskaper og annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −127,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK −127,000
Equity
NOK −91,000

Financial health · 2025

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

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

Who owns HOVED EIENDOM AS?

JNM AS
HOVED EIENDOM AS
NOK 6,000 rev. · NOK −127,000 profit

HOVED EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOVED EIENDOM AS

Who owns HOVED EIENDOM AS?

JNM AS is the largest registered owner, with 33.3%.

What is the revenue of HOVED EIENDOM AS?

HOVED EIENDOM AS had revenue of NOK 6,000 in 2025.

Where is HOVED EIENDOM AS based?

HOVED 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.