BIZTRAC BETA
Rental and operating of own or leased real estate

SØNDERSRØD EIENDOM AS

Org. no. 914543533 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 470,000
Equity NOK 2.1m
Incorporated 2014
Share capital NOK 1.2m

SØNDERSRØD EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 914543533. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Utvikling, kjøp og salg av fasteiendom og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 470,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 470,000
Equity
NOK 2.1m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns SØNDERSRØD EIENDOM AS?

MONTIS EIENDOM AS
SØNDERSRØD EIENDOM AS
NOK 1.2m rev. · NOK 470,000 profit

SØNDERSRØD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØNDERSRØD EIENDOM AS

Who owns SØNDERSRØD EIENDOM AS?

MONTIS EIENDOM AS is the largest registered owner, with 70.0%.

What is the revenue of SØNDERSRØD EIENDOM AS?

SØNDERSRØD EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of SØNDERSRØD EIENDOM AS?

Ole Håkon Øyesvold is registered as general manager of SØNDERSRØD EIENDOM AS.

Where is SØNDERSRØD EIENDOM AS based?

SØNDERSRØD EIENDOM AS has its business address in Helgeroa.

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.