biztrac. BETA
COMPANY REGISTER PROFILE
889723092 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of civilian ships and boats

ORCA MARITIME AS

Org. no. 889723092 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −298
Equity NOK 29,000
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−298 kr).

ORCA MARITIME AS is registered as a limited company in Oslo, Oslo with organisation number 889723092. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og påføring av film for overflatebehandling og korrosjonsbeskyttelse, samt deltagelse i andre selskaper med samme eller lignende formål.”.

Key figures · 2025

Operating profit
NOK −298
▲ +73 %
Equity
NOK 29,000
▲ +8 %
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns ORCA MARITIME AS?

ORCA MARITIME AS
· NOK −298 profit

ORCA MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORCA MARITIME AS own?

ORCA MARITIME AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORCA MARITIME AS

Who owns ORCA MARITIME AS?

Odd Hauge is the largest registered owner, with 100.0%.

Who is the general manager of ORCA MARITIME AS?

Odd Hauge is registered as general manager of ORCA MARITIME AS.

Where is ORCA MARITIME AS based?

ORCA MARITIME AS has its business address in Oslo.

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.