BIZTRAC BETA
Other captive investment companies

SØSTRENE KLAKEGG AS

Org. no. 926156004 Limited company (AS) Sunnfjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 171,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SØSTRENE KLAKEGG AS is registered as a limited company in Sunnfjord, Vestland with organisation number 926156004. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investeringer i aksjer og andeler, samt andre verdipapirer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 171,000
Est. value
NOK 210,000

Financial health · 2025

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

Who owns SØSTRENE KLAKEGG AS?

SOL EIKESETH KLAKEGG
SØSTRENE KLAKEGG AS
NOK 0 rev. · NOK −1,000 profit

SØSTRENE KLAKEGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØSTRENE KLAKEGG AS own?

SØSTRENE KLAKEGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØSTRENE KLAKEGG AS

Who owns SØSTRENE KLAKEGG AS?

SOL EIKESETH KLAKEGG is the largest registered owner, with 33.3%.

What is the revenue of SØSTRENE KLAKEGG AS?

SØSTRENE KLAKEGG AS had revenue of NOK 0 in 2025.

Where is SØSTRENE KLAKEGG AS based?

SØSTRENE KLAKEGG AS has its business address in Førde.

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.