BIZTRAC BETA
Development of building projects

SØRNORSK EIENDOM AS

Org. no. 911565331 Limited company (AS) Lindesnes Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 90,000
Operating profit NOK 29,000
Equity NOK 18,000
Incorporated 2013
Share capital NOK 60,000

SØRNORSK EIENDOM AS is registered as a limited company in Lindesnes, Agder with organisation number 911565331. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Investering i eiendomsprosjekter, omsetning og drift av eiendommer, herunder delta i andre selskaper som aksjeeier eller ansvarlig deltaker.”. The most recent filed accounts, for the 2024 financial year, show NOK 90,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 90,000
Operating profit
NOK 29,000
Equity
NOK 18,000
Est. value
NOK 68,000

Financial health · 2024

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

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

Who owns SØRNORSK EIENDOM AS?

FREDAM HOLDING AS
SØRNORSK EIENDOM AS
NOK 90,000 rev. · NOK 29,000 profit

SØRNORSK EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRNORSK EIENDOM AS

Who owns SØRNORSK EIENDOM AS?

FREDAM HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SØRNORSK EIENDOM AS?

SØRNORSK EIENDOM AS had revenue of NOK 90,000 in 2024.

Who is the general manager of SØRNORSK EIENDOM AS?

Fredrik Damman is registered as general manager of SØRNORSK EIENDOM AS.

Where is SØRNORSK EIENDOM AS based?

SØRNORSK EIENDOM AS has its business address in Lindesnes.

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.