BIZTRAC BETA
Development of building projects

SOLEIKNUTEN EIENDOM AS

Org. no. 916056001 Limited company (AS) Sirdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −467,000
Equity NOK 22.0m
Incorporated 2015
Share capital NOK 72,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−467k kr).

SOLEIKNUTEN EIENDOM AS is registered as a limited company in Sirdal, Agder with organisation number 916056001. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 72,000, divided into 100 shares. The company's stated purpose is: “Eie og utvikle fast eiendom, samt alt som står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −467,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −467,000
Equity
NOK 22.0m
Est. value
NOK 17.9m

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.1%
Good
Equity as a share of total capital

Who owns SOLEIKNUTEN EIENDOM AS?

SOLEIKNUTEN SKILJEGARD AS
SOLEIKNUTEN EIENDOM AS
NOK 3.0m rev. · NOK −467,000 profit

SOLEIKNUTEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLEIKNUTEN EIENDOM AS

Who owns SOLEIKNUTEN EIENDOM AS?

SOLEIKNUTEN SKILJEGARD AS is the largest registered owner, with 100.0%.

What is the revenue of SOLEIKNUTEN EIENDOM AS?

SOLEIKNUTEN EIENDOM AS had revenue of NOK 3.0m in 2024.

Who is the general manager of SOLEIKNUTEN EIENDOM AS?

Laila Helleberg is registered as general manager of SOLEIKNUTEN EIENDOM AS.

Where is SOLEIKNUTEN EIENDOM AS based?

SOLEIKNUTEN EIENDOM AS has its business address in Tjørhom.

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.