BIZTRAC BETA
Uoppgitt

KVENNBEKKHAUGEN HOLDING AS

Org. no. 923461566 Limited company (AS) Tynset Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 2.3m
Incorporated 2019
Share capital NOK 33,000

Signals

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

KVENNBEKKHAUGEN HOLDING AS is registered as a limited company in Tynset, Innlandet with organisation number 923461566. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 33,000, divided into 275750 shares. The company's stated purpose is: “Investering, eierskap og salg av selskapsandeler, obligasjoner og øvrige finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 2.3m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns KVENNBEKKHAUGEN HOLDING AS?

MARIT MJØEN SOLEM
KVENNBEKKHAUGEN HOLDING AS
NOK 0 rev. · NOK −28,000 profit

KVENNBEKKHAUGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVENNBEKKHAUGEN HOLDING AS own?

KVENNBEKKHAUGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KVENNBEKKHAUGEN HOLDING AS

Who owns KVENNBEKKHAUGEN HOLDING AS?

MARIT MJØEN SOLEM is the largest registered owner, with 100.0%.

What is the revenue of KVENNBEKKHAUGEN HOLDING AS?

KVENNBEKKHAUGEN HOLDING AS had revenue of NOK 0 in 2025.

Where is KVENNBEKKHAUGEN HOLDING AS based?

KVENNBEKKHAUGEN HOLDING AS has its business address in Kvikne.

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.