BIZTRAC BETA
Other captive investment companies

LKL HOLDING AS

Org. no. 912603008 Limited company (AS) Fredrikstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 1.6m
Incorporated 2013
Share capital NOK 32,000

Signals

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

LKL HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 912603008. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 32,000, divided into 63 shares. The company's stated purpose is: “Å eie aksjer og andeler og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 1.6m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns LKL HOLDING AS?

KJERSTI BODAHL HAUGE
LKL HOLDING AS
NOK 0 rev. · NOK −14,000 profit

LKL HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LKL HOLDING AS own?

LKL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LKL HOLDING AS

Who owns LKL HOLDING AS?

KJERSTI BODAHL HAUGE is the largest registered owner, with 33.3%.

What is the revenue of LKL HOLDING AS?

LKL HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of LKL HOLDING AS?

Kjersti Bodahl Hauge is registered as general manager of LKL HOLDING AS.

Where is LKL HOLDING AS based?

LKL HOLDING AS has its business address in Kråkerøy.

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.