BIZTRAC BETA
COMPANY REGISTER PROFILE
925929743 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

NORDIC OCEAN MANAGEMENT AS

Org. no. 925929743 Limited company (AS) Øygarden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 1.4m
Incorporated 2020
Share capital NOK 681,000

Signals

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

NORDIC OCEAN MANAGEMENT AS is registered as a limited company in Øygarden, Vestland with organisation number 925929743. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 681,000, divided into 681000 shares. The company's stated purpose is: “Foreta investeringer primært innen sjøfart og den maritime næring samt foreta kjøp og salg av aksjer og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 1.4m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns NORDIC OCEAN MANAGEMENT AS?

JONAS BLOMBERG
NORDIC OCEAN MANAGEMENT AS
NOK 0 rev. · NOK −9,000 profit

NORDIC OCEAN MANAGEMENT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDIC OCEAN MANAGEMENT AS

Who owns NORDIC OCEAN MANAGEMENT AS?

JONAS BLOMBERG is the largest registered owner, with 50.0%.

What is the revenue of NORDIC OCEAN MANAGEMENT AS?

NORDIC OCEAN MANAGEMENT AS had revenue of NOK 0 in 2025.

Where is NORDIC OCEAN MANAGEMENT AS based?

NORDIC OCEAN MANAGEMENT AS has its business address in Ågotnes.

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.