BIZTRAC BETA
Other real estate activities on a fee or contract basis

SOLEIKNUTEN SKILJEGARD AS

Org. no. 915960251 Limited company (AS) Sirdal Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −149,000
Equity NOK 49.6m
Incorporated 2015
Share capital NOK 100,000

Signals

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

SOLEIKNUTEN SKILJEGARD AS is registered as a limited company in Sirdal, Agder with organisation number 915960251. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt alt som står i den forbindelse.”.

Key figures · 2024

Operating profit
NOK −149,000
Equity
NOK 49.6m
Est. value
NOK 131.8m

Financial health · 2024

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

Who owns SOLEIKNUTEN SKILJEGARD AS?

LAILA HELLEBERG
SOLEIKNUTEN SKILJEGARD AS
· NOK −149,000 profit

SOLEIKNUTEN SKILJEGARD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLEIKNUTEN SKILJEGARD AS own?

SOLEIKNUTEN SKILJEGARD AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

SOLEIKNUTEN SKILJEGARD AS er morselskap for 1 datterselskap:

Frequently asked questions about SOLEIKNUTEN SKILJEGARD AS

Who owns SOLEIKNUTEN SKILJEGARD AS?

LAILA HELLEBERG is the largest registered owner, with 100.0%.

Who is the general manager of SOLEIKNUTEN SKILJEGARD AS?

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

Where is SOLEIKNUTEN SKILJEGARD AS based?

SOLEIKNUTEN SKILJEGARD 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.