BIZTRAC BETA
Other captive investment companies

STØLE THERKELSEN EIENDOM AS

Org. no. 989234404 Limited company (AS) Lyngdal Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −65,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 30,000

Signals

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

STØLE THERKELSEN EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 989234404. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå investering i aksjer, obligasjoner, selskapsandeler og andre verdipapirer, samt erverv, utvikling, forvaltning og omsetning av faste eiendommer og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −65,000
Equity
NOK 1.8m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns STØLE THERKELSEN EIENDOM AS?

BIRGITTE STØLE THERKELSEN
STØLE THERKELSEN EIENDOM AS
· NOK −65,000 profit

STØLE THERKELSEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does STØLE THERKELSEN EIENDOM AS own?

STØLE THERKELSEN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STØLE THERKELSEN EIENDOM AS

Who owns STØLE THERKELSEN EIENDOM AS?

BIRGITTE STØLE THERKELSEN is the largest registered owner, with 85.0%.

Where is STØLE THERKELSEN EIENDOM AS based?

STØLE THERKELSEN EIENDOM AS has its business address in Lyngdal.

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.