BIZTRAC BETA
Support activities for fishing and aquaculture

ØREN AQUASERVICE AS

Org. no. 929210506 Limited company (AS) Nærøysund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 800
Operating profit NOK −13,000
Equity NOK 51,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

ØREN AQUASERVICE AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 929210506. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tjenester tilknyttet hav- og kystbasert akvakultur.”. The most recent filed accounts, for the 2025 financial year, show NOK 800 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 800
Operating profit
NOK −13,000
Equity
NOK 51,000
Est. value
NOK 24,000

Financial health · 2024

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

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

Who owns ØREN AQUASERVICE AS?

BRAGE ØREN
ØREN AQUASERVICE AS
NOK 800 rev. · NOK −13,000 profit

ØREN AQUASERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØREN AQUASERVICE AS

Who owns ØREN AQUASERVICE AS?

BRAGE ØREN is the largest registered owner, with 100.0%.

What is the revenue of ØREN AQUASERVICE AS?

ØREN AQUASERVICE AS had revenue of NOK 800 in 2025.

Who is the general manager of ØREN AQUASERVICE AS?

Brage Øren is registered as general manager of ØREN AQUASERVICE AS.

Where is ØREN AQUASERVICE AS based?

ØREN AQUASERVICE AS has its business address in Kolvereid.

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.