BIZTRAC BETA
Sewerage

AKERSHUS MILJØ AS

Org. no. 914094399 Limited company (AS) Frogn Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 33.6m
Operating profit NOK −3.8m
Equity NOK 9.0m
Incorporated 2014
Employees 14
Share capital NOK 110,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,8 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AKERSHUS MILJØ AS is registered as a limited company in Frogn, Akershus with organisation number 914094399. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2014 and has 14 registered employees. Registered share capital is NOK 110,000, divided into 110 shares. The company's stated purpose is: “Oppsamling og behandling av avløpsvann.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.6m in revenue and NOK −3.8m in operating profit.

Key figures · 2024

Revenue
NOK 33.6m
Operating profit
NOK −3.8m
Equity
NOK 9.0m
Est. value
NOK 26.2m

Financial health · 2024

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

Who owns AKERSHUS MILJØ AS?

KAX HOLDING AS
AKERSHUS MILJØ AS
NOK 33.6m rev. · NOK −3.8m profit

AKERSHUS MILJØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKERSHUS MILJØ AS

Who owns AKERSHUS MILJØ AS?

KAX HOLDING AS is the largest registered owner, with 69.1%.

What is the revenue of AKERSHUS MILJØ AS?

AKERSHUS MILJØ AS had revenue of NOK 33.6m in 2024.

Who is the general manager of AKERSHUS MILJØ AS?

Ole-Martin Kaxrud is registered as general manager of AKERSHUS MILJØ AS.

Where is AKERSHUS MILJØ AS based?

AKERSHUS MILJØ AS has its business address in Drøbak.

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.