BIZTRAC BETA
Uoppgitt

KLARA OLAVA HOLDING AS

Org. no. 926328344 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −1,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 30,000

Signals

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

KLARA OLAVA HOLDING AS is registered as a limited company in Lørenskog, Akershus with organisation number 926328344. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −1,000
Equity
NOK 1.0m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns KLARA OLAVA HOLDING AS?

MARCUS GJERMUNDSHAUG
KLARA OLAVA HOLDING AS
NOK 10,000 rev. · NOK −1,000 profit

KLARA OLAVA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KLARA OLAVA HOLDING AS own?

KLARA OLAVA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KLARA OLAVA HOLDING AS

Who owns KLARA OLAVA HOLDING AS?

MARCUS GJERMUNDSHAUG is the largest registered owner, with 50.0%.

What is the revenue of KLARA OLAVA HOLDING AS?

KLARA OLAVA HOLDING AS had revenue of NOK 10,000 in 2024.

Where is KLARA OLAVA HOLDING AS based?

KLARA OLAVA HOLDING AS has its business address in Fjellhamar.

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.