BIZTRAC BETA
Other building and industrial cleaning activities

NIWI MILJØTILTAK AS

Org. no. 964280592 Limited company (AS) Bærum Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 848,000
Equity NOK 2.8m
Incorporated 1992
Employees 8
Share capital NOK 200,000

NIWI MILJØTILTAK AS is registered as a limited company in Bærum, Akershus with organisation number 964280592. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 1992 and has 8 registered employees. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Renovasjonstjenester, servicevirksomhet og salg, og annen virksomhet som står i forbindelse hermed, herunder deltagelse i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 848,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.5m
Operating profit
NOK 848,000
Equity
NOK 2.8m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns NIWI MILJØTILTAK AS?

KAARE STEINMO
NIWI MILJØTILTAK AS
NOK 12.5m rev. · NOK 848,000 profit

NIWI MILJØTILTAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIWI MILJØTILTAK AS

Who owns NIWI MILJØTILTAK AS?

KAARE STEINMO is the largest registered owner, with 100.0%.

What is the revenue of NIWI MILJØTILTAK AS?

NIWI MILJØTILTAK AS had revenue of NOK 12.5m in 2025.

Who is the general manager of NIWI MILJØTILTAK AS?

Kaare Steinmo is registered as general manager of NIWI MILJØTILTAK AS.

Where is NIWI MILJØTILTAK AS based?

NIWI MILJØTILTAK AS has its business address in Fornebu.

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.