biztrac. BETA
COMPANY REGISTER PROFILE
995665794 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

AZOREA AS

Org. no. 995665794 Limited company (AS) Fjord Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 1.3m
Equity NOK 374,000
Incorporated 2010
Share capital NOK 200,000

AZOREA AS is registered as a limited company in Fjord, Møre og Romsdal with organisation number 995665794. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Selskapets formål er å drive virksomhet med omsetning av varer og tjenester, drive virksomhet med å investere i fast eiendom og aksjer, utleie av fast eiendom samt å delta i annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
▲ +19 %
Operating profit
NOK 1.3m
▲ +236 %
Equity
NOK 374,000
▼ −26 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
112.1%
Very good
Return on total assets
Solidity
30.7%
Good
Equity as a share of total capital

Who owns AZOREA AS?

AZOREA AS
NOK 3.3m rev. · NOK 1.3m profit

AZOREA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AZOREA AS

Who owns AZOREA AS?

Marit Elisabeth Døving is the largest registered owner, with 50.0%.

What is the revenue of AZOREA AS?

AZOREA AS had revenue of NOK 3.3m in 2025.

Who is the general manager of AZOREA AS?

Marit Elisabeth Døving is registered as general manager of AZOREA AS.

Where is AZOREA AS based?

AZOREA AS has its business address in Valldal.

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.