BIZTRAC BETA
General cleaning of buildings

NORSK INDUSTRIVASK AS

Org. no. 994180215 Limited company (AS) Nittedal Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 25.2m
Operating profit NOK 1.4m
Equity NOK 345,000
Incorporated 2009
Employees 51
Share capital NOK 200,000

NORSK INDUSTRIVASK AS is registered as a limited company in Nittedal, Akershus with organisation number 994180215. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2009 and has 51 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Rengjøring og annen virksomhet i tilknytning til dette og deltakelse i andre selskaper ved tegning av aksjer eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 25.2m
Operating profit
NOK 1.4m
Equity
NOK 345,000
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns NORSK INDUSTRIVASK AS?

MC CLEAN HOLDING AS
NORSK INDUSTRIVASK AS
NOK 25.2m rev. · NOK 1.4m profit

NORSK INDUSTRIVASK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK INDUSTRIVASK AS

Who owns NORSK INDUSTRIVASK AS?

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

What is the revenue of NORSK INDUSTRIVASK AS?

NORSK INDUSTRIVASK AS had revenue of NOK 25.2m in 2025.

Who is the general manager of NORSK INDUSTRIVASK AS?

Thor-Kristian Sundquist is registered as general manager of NORSK INDUSTRIVASK AS.

Where is NORSK INDUSTRIVASK AS based?

NORSK INDUSTRIVASK AS has its business address in Slattum.

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.