biztrac. BETA
COMPANY REGISTER PROFILE
997587154 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicle parts and accessories

MYHRE OLSEN HOLDING AS

Org. no. 997587154 Limited company (AS) Alstahaug Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −32,000
Equity NOK 3.5m
Incorporated 2011
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).
  • Nylig endring 2026-09-29 Adresseendring registrert 2026-09-29.

MYHRE OLSEN HOLDING AS is registered as a limited company in Alstahaug, Nordland with organisation number 997587154. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2011. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Eie aksjer og andeler i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −32,000
▲ +35 %
Equity
NOK 3.5m
▼ −5 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
61.9%
Very good
Equity as a share of total capital

Who owns MYHRE OLSEN HOLDING AS?

MYHRE OLSEN HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MYHRE OLSEN HOLDING AS own?

MYHRE OLSEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about MYHRE OLSEN HOLDING AS

Who owns MYHRE OLSEN HOLDING AS?

Bjarne Jørgen Myhre Olsen is the largest registered owner, with 90.0%.

Who is the general manager of MYHRE OLSEN HOLDING AS?

Bjarne Jørgen Myhre Olsen is registered as general manager of MYHRE OLSEN HOLDING AS.

Where is MYHRE OLSEN HOLDING AS based?

MYHRE OLSEN HOLDING AS has its business address in Sandnessjøen.

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.