biztrac. BETA
COMPANY REGISTER PROFILE
989148125 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

LCK HOLDING AS

Org. no. 989148125 Limited company (AS) Stavanger Incorporated 2005 Active
Operating profit NOK −184,000
Equity NOK 1.3m
Incorporated 2005
Share capital NOK 100,000

Signals

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

LCK HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 989148125. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Forvaltning av eierskap i andre virksomheter, herunder kjøp og salg av aksjer i eksisterende virksomheter og deltakelse i nyetablering av virksomheter.”.

Key figures · 2025

Operating profit
NOK −184,000
▼ −610 %
Equity
NOK 1.3m
▲ +71 %
Est. value
NOK 89.6m

Financial health · 2025

Liquidity
58.79
Very good
Current assets ÷ current liabilities
Profitability
1209.6%
Very good
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns LCK HOLDING AS?

LCK HOLDING AS
· NOK −184,000 profit

LCK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LCK HOLDING AS own?

LCK HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

LCK HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about LCK HOLDING AS

Who owns LCK HOLDING AS?

Linda Cecilie Langvik is the largest registered owner, with 100.0%.

Who is the general manager of LCK HOLDING AS?

Linda Cecilie Langvik is registered as general manager of LCK HOLDING AS.

Where is LCK HOLDING AS based?

LCK HOLDING AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.