BIZTRAC BETA
Rental and operating of own or leased real estate

KVALSVIK EIGEDOM AS

Org. no. 992627085 Limited company (AS) Vanylven Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 623,000
Equity NOK 3.5m
Incorporated 2008
Share capital NOK 186,000

KVALSVIK EIGEDOM AS is registered as a limited company in Vanylven, Møre og Romsdal with organisation number 992627085. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 186,000, divided into 186 shares. The company's stated purpose is: “Utleie og forvaltning av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 623,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 623,000
Equity
NOK 3.5m
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns KVALSVIK EIGEDOM AS?

KJELL-ARNE KVALSVIK
KVALSVIK EIGEDOM AS
NOK 1.1m rev. · NOK 623,000 profit

KVALSVIK EIGEDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KVALSVIK EIGEDOM AS own?

KVALSVIK EIGEDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KVALSVIK EIGEDOM AS

Who owns KVALSVIK EIGEDOM AS?

KJELL-ARNE KVALSVIK is the largest registered owner, with 53.2%.

What is the revenue of KVALSVIK EIGEDOM AS?

KVALSVIK EIGEDOM AS had revenue of NOK 1.1m in 2024.

Who is the general manager of KVALSVIK EIGEDOM AS?

Tor Inge Kvalsvik is registered as general manager of KVALSVIK EIGEDOM AS.

Where is KVALSVIK EIGEDOM AS based?

KVALSVIK EIGEDOM AS has its business address in Fiskå.

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.