BIZTRAC BETA
Business and other management consultancy activities

OCEANPRO ENVIRONMENT AS

Org. no. 934797345 Limited company (AS) Flatanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 25,000
Incorporated 2024
Share capital NOK 60,000

OCEANPRO ENVIRONMENT AS is registered as a limited company in Flatanger, Trøndelag with organisation number 934797345. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 6000 shares. The company's stated purpose is: “Rådgivning, tjenesteyting og salg av konsulenttjenester til havbruksnæringen.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 25,000
Est. value
NOK 25,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OCEANPRO ENVIRONMENT AS?

OCEANPRO AS
OCEANPRO ENVIRONMENT AS
NOK 0 rev. · NOK 0 profit

OCEANPRO ENVIRONMENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OCEANPRO ENVIRONMENT AS

Who owns OCEANPRO ENVIRONMENT AS?

OCEANPRO AS is the largest registered owner, with 80.0%.

What is the revenue of OCEANPRO ENVIRONMENT AS?

OCEANPRO ENVIRONMENT AS had revenue of NOK 0 in 2024.

Who is the general manager of OCEANPRO ENVIRONMENT AS?

Alexander Strøm Lindseth is registered as general manager of OCEANPRO ENVIRONMENT AS.

Where is OCEANPRO ENVIRONMENT AS based?

OCEANPRO ENVIRONMENT AS has its business address in Flatanger.

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.