BIZTRAC BETA
Uoppgitt

ONE BLUE OCEAN AS

Org. no. 921961391 Limited company (AS) Herøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −60
Equity NOK 17,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

ONE BLUE OCEAN AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 921961391. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −60 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −60
Equity
NOK 17,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns ONE BLUE OCEAN AS?

JUNE ANITA VÅGSHOLM ROONEY
ONE BLUE OCEAN AS
NOK 0 rev. · NOK −60 profit

ONE BLUE OCEAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ONE BLUE OCEAN AS

Who owns ONE BLUE OCEAN AS?

JUNE ANITA VÅGSHOLM ROONEY is the largest registered owner, with 100.0%.

What is the revenue of ONE BLUE OCEAN AS?

ONE BLUE OCEAN AS had revenue of NOK 0 in 2025.

Who is the general manager of ONE BLUE OCEAN AS?

June Anita Vågsholm Rooney is registered as general manager of ONE BLUE OCEAN AS.

Where is ONE BLUE OCEAN AS based?

ONE BLUE OCEAN AS has its business address in Fosnavåg.

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.