BIZTRAC BETA
Business and other management consultancy activities

PROCONOMY AS

Org. no. 918901280 Limited company (AS) Haugesund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2,000
Operating profit NOK −10,000
Equity NOK 706,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

PROCONOMY AS is registered as a limited company in Haugesund, Rogaland with organisation number 918901280. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Forretningsutvikling, interimsledelse, rådgivning, konsulentvirksomhet, personalutleie og rekruttering, primært innen helsebransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 2,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 2,000
Operating profit
NOK −10,000
Equity
NOK 706,000
Est. value
NOK 347,000

Financial health · 2024

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

Who owns PROCONOMY AS?

BJØRN MIKAL HENRIKSEN
PROCONOMY AS
NOK 2,000 rev. · NOK −10,000 profit

PROCONOMY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROCONOMY AS

Who owns PROCONOMY AS?

BJØRN MIKAL HENRIKSEN is the largest registered owner, with 100.0%.

What is the revenue of PROCONOMY AS?

PROCONOMY AS had revenue of NOK 2,000 in 2024.

Who is the general manager of PROCONOMY AS?

Bjørn Mikal Henriksen is registered as general manager of PROCONOMY AS.

Where is PROCONOMY AS based?

PROCONOMY AS has its business address in Haugesund.

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.