BIZTRAC BETA
COMPANY REGISTER PROFILE
934077989 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

OCEAN ORAKEL SERVICE AS

Org. no. 934077989 Limited company (AS) Alta Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −2,000
Equity NOK 417,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

OCEAN ORAKEL SERVICE AS is registered as a limited company in Alta, Finnmark with organisation number 934077989. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bemanning.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −2,000
Equity
NOK 417,000
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.4%
Good
Equity as a share of total capital

Who owns OCEAN ORAKEL SERVICE AS?

ALEXANDER VESTRE
OCEAN ORAKEL SERVICE AS
NOK 2.2m rev. · NOK −2,000 profit

OCEAN ORAKEL SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCEAN ORAKEL SERVICE AS

Who owns OCEAN ORAKEL SERVICE AS?

ALEXANDER VESTRE is the largest registered owner, with 100.0%.

What is the revenue of OCEAN ORAKEL SERVICE AS?

OCEAN ORAKEL SERVICE AS had revenue of NOK 2.2m in 2025.

Who is the general manager of OCEAN ORAKEL SERVICE AS?

Alexander Vestre is registered as general manager of OCEAN ORAKEL SERVICE AS.

Where is OCEAN ORAKEL SERVICE AS based?

OCEAN ORAKEL SERVICE AS has its business address in Alta.

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.