biztrac. BETA
COMPANY REGISTER PROFILE
948230798 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other support activities for petroleum and natural gas extraction

DEEPOCEAN MARITIME AS

Org. no. 948230798 Limited company (AS) Haugesund Incorporated 1986 Active
Ownership graph ↗
Operating profit NOK −1.4m
Equity NOK 3.2m
Incorporated 1986
Share capital NOK 51,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,4 mill kr).

DEEPOCEAN MARITIME AS is registered as a limited company in Haugesund, Rogaland with organisation number 948230798. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 1986. Registered share capital is NOK 51,000, divided into 5126500 shares. The company's stated purpose is: “Produksjon, tjenesteyting og handel i tilknytning til undervannsvirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”.

Former names: OCEANTEAM AS, DO BERGEN AS

Key figures · 2025

Operating profit
NOK −1.4m
▲ +47 %
Equity
NOK 3.2m
▼ −2 %
Est. value
NOK 3.2m

Financial health · 2025

Liquidity
6.72
Very good
Current assets ÷ current liabilities
Profitability
-32.0%
Not satisfactory
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns DEEPOCEAN MARITIME AS?

DEEPOCEAN MARITIME AS
· NOK −1.4m profit

DEEPOCEAN MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEEPOCEAN MARITIME AS

Who owns DEEPOCEAN MARITIME AS?

DEEPOCEAN AS is the largest registered owner, with 100.0%.

Who is the general manager of DEEPOCEAN MARITIME AS?

Frode Garlid is registered as general manager of DEEPOCEAN MARITIME AS.

Where is DEEPOCEAN MARITIME AS based?

DEEPOCEAN MARITIME AS has its business address in Haugesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.