BIZTRAC BETA
Rental and operating of own or leased real estate

SOLLISTRAND EIENDOM AS

Org. no. 833237802 Limited company (AS) Horten Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 1.2m
Equity NOK 20.7m
Incorporated 1982
Share capital NOK 300,000

SOLLISTRAND EIENDOM AS is registered as a limited company in Horten, Vestfold with organisation number 833237802. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 300,000. The company's stated purpose is: “Produksjon og handel samt kjøp, samt kjøp, salg, besittelse og drift av faste eiendommer. Herunder kan selskapet gjennom aksjeerverv eller på annen måte delta i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 1.2m
Equity
NOK 20.7m
Est. value
NOK 16.7m

Financial health · 2024

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

Who owns SOLLISTRAND EIENDOM AS?

FLAVIA AS
SOLLISTRAND EIENDOM AS
NOK 6.9m rev. · NOK 1.2m profit

SOLLISTRAND EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLLISTRAND EIENDOM AS

Who owns SOLLISTRAND EIENDOM AS?

FLAVIA AS is the largest registered owner, with 89.3%.

What is the revenue of SOLLISTRAND EIENDOM AS?

SOLLISTRAND EIENDOM AS had revenue of NOK 6.9m in 2024.

Who is the general manager of SOLLISTRAND EIENDOM AS?

Dag Kjeldsberg is registered as general manager of SOLLISTRAND EIENDOM AS.

Where is SOLLISTRAND EIENDOM AS based?

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