BIZTRAC BETA
Other technical consultancy

BJARHO AS

Org. no. 920951953 Limited company (AS) Alver Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 849,000
Operating profit NOK −72,000
Equity NOK 536,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

BJARHO AS is registered as a limited company in Alver, Vestland with organisation number 920951953. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikle og selge produkter og tjenester. Primærmarkedet er landbasert industri og oljebransjen. Denne aktiviteten vil også kunne omfatte handel, agenturvirksomhet, kjøp av aksjer og andeler i andre foretak, samt alt som er forbundet dermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 849,000 in revenue and NOK −72,000 in operating profit.

Key figures · 2024

Revenue
NOK 849,000
Operating profit
NOK −72,000
Equity
NOK 536,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns BJARHO AS?

BJØRN ARILD HOLMEN
BJARHO AS
NOK 849,000 rev. · NOK −72,000 profit

BJARHO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJARHO AS

Who owns BJARHO AS?

BJØRN ARILD HOLMEN is the largest registered owner, with 100.0%.

What is the revenue of BJARHO AS?

BJARHO AS had revenue of NOK 849,000 in 2024.

Who is the general manager of BJARHO AS?

Bjørn Arild Holmen is registered as general manager of BJARHO AS.

Where is BJARHO AS based?

BJARHO AS has its business address in Rossland.

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.