BIZTRAC BETA
Collection of non-hazardous waste

KLM MILJØ AS

Org. no. 877172112 Limited company (AS) Eidsvoll Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 28.6m
Operating profit NOK 1.2m
Equity NOK 4.3m
Incorporated 1997
Employees 9
Share capital NOK 2.4m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KLM MILJØ AS is registered as a limited company in Eidsvoll, Akershus with organisation number 877172112. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 1997 and has 9 registered employees. Registered share capital is NOK 2.4m, divided into 2393000 shares. The company's stated purpose is: “Drive virksomhet innen renovasjon, herunder avfallsbehandling og- gjennvinning og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 28.6m
Operating profit
NOK 1.2m
Equity
NOK 4.3m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns KLM MILJØ AS?

MILJØVAKTA AS
KLM MILJØ AS
NOK 28.6m rev. · NOK 1.2m profit

KLM MILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLM MILJØ AS

Who owns KLM MILJØ AS?

MILJØVAKTA AS is the largest registered owner, with 100.0%.

What is the revenue of KLM MILJØ AS?

KLM MILJØ AS had revenue of NOK 28.6m in 2024.

Who is the general manager of KLM MILJØ AS?

Fred Ytterdahl is registered as general manager of KLM MILJØ AS.

Where is KLM MILJØ AS based?

KLM MILJØ AS has its business address in Minnesund.

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.