BIZTRAC BETA
Uoppgitt

KLO HOLDING AS

Org. no. 932760096 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 12,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KLO HOLDING AS is registered as a limited company in Lørenskog, Akershus with organisation number 932760096. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskap og utøve bedriftsrådgivning og annen administrativ rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 12,000
Est. value
NOK 14,000

Financial health · 2024

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KLO HOLDING AS?

KJERSTI LOHNE
KLO HOLDING AS
NOK 0 rev. · NOK −13,000 profit

KLO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KLO HOLDING AS own?

KLO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLO HOLDING AS

Who owns KLO HOLDING AS?

KJERSTI LOHNE is the largest registered owner, with 100.0%.

What is the revenue of KLO HOLDING AS?

KLO HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of KLO HOLDING AS?

Kjersti Lohne is registered as general manager of KLO HOLDING AS.

Where is KLO HOLDING AS based?

KLO HOLDING AS has its business address in Lørenskog.

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.