BIZTRAC BETA
Rental and operating of own or leased real estate

KVÅL INDUSTRIPARK AS

Org. no. 995879328 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 955,000
Equity NOK 1.3m
Incorporated 2010
Share capital NOK 600,000

KVÅL INDUSTRIPARK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 995879328. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 600,000, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse, inkludert utleie av egen eller leid fast eiendom ellers.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 955,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 955,000
Equity
NOK 1.3m
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.4%
Satisfactory
Equity as a share of total capital

Who owns KVÅL INDUSTRIPARK AS?

KRIGSVOLL HOLDING AS
KVÅL INDUSTRIPARK AS
NOK 2.4m rev. · NOK 955,000 profit

KVÅL INDUSTRIPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVÅL INDUSTRIPARK AS

Who owns KVÅL INDUSTRIPARK AS?

KRIGSVOLL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KVÅL INDUSTRIPARK AS?

KVÅL INDUSTRIPARK AS had revenue of NOK 2.4m in 2025.

Who is the general manager of KVÅL INDUSTRIPARK AS?

Anders Krigsvoll is registered as general manager of KVÅL INDUSTRIPARK AS.

Where is KVÅL INDUSTRIPARK AS based?

KVÅL INDUSTRIPARK AS has its business address in Flatåsen.

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.