BIZTRAC BETA
Business and other management consultancy activities

PROMIA AS

Org. no. 995504359 Limited company (AS) Aukra Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 57,000
Operating profit NOK 17,000
Equity NOK 2.7m
Incorporated 2010
Share capital NOK 30,000

PROMIA AS is registered as a limited company in Aukra, Møre og Romsdal with organisation number 995504359. 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 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og utvikle selskap innen energiproduksjon og tilhørende tjenester, eierskap i andre selskaper, eiendomsutvikling, konsulenttjenester, utførelse av musikk samt utleie av arbeidskraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 57,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 57,000
Operating profit
NOK 17,000
Equity
NOK 2.7m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns PROMIA AS?

IVAR HELGE HOLLEN
PROMIA AS
NOK 57,000 rev. · NOK 17,000 profit

PROMIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PROMIA AS own?

PROMIA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PROMIA AS

Who owns PROMIA AS?

IVAR HELGE HOLLEN is the largest registered owner, with 100.0%.

What is the revenue of PROMIA AS?

PROMIA AS had revenue of NOK 57,000 in 2024.

Who is the general manager of PROMIA AS?

Ivar Helge Hollen is registered as general manager of PROMIA AS.

Where is PROMIA AS based?

PROMIA AS has its business address in Molde.

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.