BIZTRAC BETA
Materials recovery

OCEANIZE AS

Org. no. 997311388 Limited company (AS) Nærøysund Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 46.1m
Operating profit NOK −33.6m
Equity NOK 1.5m
Incorporated 2011
Employees 14
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−33,6 mill kr).

OCEANIZE AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 997311388. The business is classified under materials recovery (NACE 38.210). The company was incorporated in 2011 and has 14 registered employees. Registered share capital is NOK 1.5m, divided into 15000 shares. The company's stated purpose is: “Utleie av containere, innsamling og omsetning av alle typer avfall og annen virksomhet i tilknytning til dette, herunder deltakelse i annen virksomhet ved aksjebesittelse eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.1m in revenue and NOK −33.6m in operating profit.

Key figures · 2024

Revenue
NOK 46.1m
Operating profit
NOK −33.6m
Equity
NOK 1.5m
Est. value
NOK 22.5m

Financial health · 2024

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.6%
Not satisfactory
Equity as a share of total capital

Who owns OCEANIZE AS?

MOEN INDUSTRIER AS
OCEANIZE AS
NOK 46.1m rev. · NOK −33.6m profit

OCEANIZE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCEANIZE AS

Who owns OCEANIZE AS?

MOEN INDUSTRIER AS is the largest registered owner, with 100.0%.

What is the revenue of OCEANIZE AS?

OCEANIZE AS had revenue of NOK 46.1m in 2024.

Who is the general manager of OCEANIZE AS?

Dagfinn Hammer is registered as general manager of OCEANIZE AS.

Where is OCEANIZE AS based?

OCEANIZE AS has its business address in Ottersøy.

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.