BIZTRAC BETA
Demolition

MILJØSANERING NORD AS

Org. no. 928084825 Limited company (AS) Alta Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 152.7m
Operating profit NOK 3.8m
Equity NOK 8.3m
Incorporated 2021
Employees 41
Share capital NOK 2.0m

MILJØSANERING NORD AS is registered as a limited company in Alta, Finnmark with organisation number 928084825. The business is classified under demolition (NACE 43.110). The company was incorporated in 2021 and has 41 registered employees. Registered share capital is NOK 2.0m, divided into 200 shares. The company's stated purpose is: “Utføre oppdrag vedrørende sanering, gjenvinning og rivning innen bygg og anlegg. Og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 152.7m in revenue and NOK 3.8m in operating profit.

Key figures · 2024

Revenue
NOK 152.7m
Operating profit
NOK 3.8m
Equity
NOK 8.3m
Est. value
NOK 15.0m

Financial health · 2024

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

Who owns MILJØSANERING NORD AS?

TT3 HOLDING AS
MILJØSANERING NORD AS
NOK 152.7m rev. · NOK 3.8m profit

MILJØSANERING NORD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MILJØSANERING NORD AS

Who owns MILJØSANERING NORD AS?

TT3 HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of MILJØSANERING NORD AS?

MILJØSANERING NORD AS had revenue of NOK 152.7m in 2024.

Who is the general manager of MILJØSANERING NORD AS?

Thomas Mathias Thomassen is registered as general manager of MILJØSANERING NORD AS.

Where is MILJØSANERING NORD AS based?

MILJØSANERING NORD AS has its business address in Alta.

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.