BIZTRAC BETA
Uoppgitt

KVITNESET HOLDING AS

Org. no. 920540783 Limited company (AS) Kristiansund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 432,000
Operating profit NOK 76,000
Equity NOK 578,000
Incorporated 2018
Share capital NOK 30,000

KVITNESET HOLDING AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 920540783. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Helsetjenester, herunder spesialiserte legetjenester,samt vedproduksjon og annet arbeide innen jord og skog, investering i andre selskaper og annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 432,000 in revenue and NOK 76,000 in operating profit.

Key figures · 2024

Revenue
NOK 432,000
Operating profit
NOK 76,000
Equity
NOK 578,000
Est. value
NOK 609,000

Financial health · 2024

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

Who owns KVITNESET HOLDING AS?

PER OLAV HOEM KVALVÅG
KVITNESET HOLDING AS
NOK 432,000 rev. · NOK 76,000 profit

KVITNESET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVITNESET HOLDING AS own?

KVITNESET HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KVITNESET HOLDING AS

Who owns KVITNESET HOLDING AS?

PER OLAV HOEM KVALVÅG is the largest registered owner, with 100.0%.

What is the revenue of KVITNESET HOLDING AS?

KVITNESET HOLDING AS had revenue of NOK 432,000 in 2024.

Where is KVITNESET HOLDING AS based?

KVITNESET HOLDING AS has its business address in Kristiansund N.

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.