BIZTRAC BETA
Rental and operating of own or leased real estate

SKAGERAK EIENDOM AS

Org. no. 924780711 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −80,000
Equity NOK 14.7m
Incorporated 2020
Share capital NOK 17.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−80k kr).

SKAGERAK EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 924780711. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 17.1m, divided into 60 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer og dertil tilknyttet virksomhet, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −80,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −80,000
Equity
NOK 14.7m
Est. value
NOK 13.4m

Financial health · 2025

Liquidity
0.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Good
Equity as a share of total capital

Who owns SKAGERAK EIENDOM AS?

DUVHOLT AS
SKAGERAK EIENDOM AS
NOK 0 rev. · NOK −80,000 profit

SKAGERAK EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SKAGERAK EIENDOM AS own?

SKAGERAK EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SKAGERAK EIENDOM AS

Who owns SKAGERAK EIENDOM AS?

DUVHOLT AS is the largest registered owner, with 50.0%.

What is the revenue of SKAGERAK EIENDOM AS?

SKAGERAK EIENDOM AS had revenue of NOK 0 in 2025.

Where is SKAGERAK EIENDOM AS based?

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