biztrac. BETA
COMPANY REGISTER PROFILE
932251175 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MINDOR HOBBERSTAD HOLDING AS

Org. no. 932251175 Limited company (AS) Bjerkreim Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 317,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

MINDOR HOBBERSTAD HOLDING AS is registered as a limited company in Bjerkreim, Rogaland with organisation number 932251175. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer og andre produkter og tjenester som naturlig hører sammen med dette.”.

Key figures · 2025

Operating profit
NOK −6,000
▲ +0 %
Equity
NOK 317,000
▲ +121 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
40.1%
Very good
Return on total assets
Solidity
69.9%
Very good
Equity as a share of total capital

Who owns MINDOR HOBBERSTAD HOLDING AS?

MINDOR HOBBERSTAD HOLDING AS
· NOK −6,000 profit

MINDOR HOBBERSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MINDOR HOBBERSTAD HOLDING AS own?

MINDOR HOBBERSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MINDOR HOBBERSTAD HOLDING AS

Who owns MINDOR HOBBERSTAD HOLDING AS?

Mindor Hobberstad is the largest registered owner, with 100.0%.

Who is the general manager of MINDOR HOBBERSTAD HOLDING AS?

Mindor Hobberstad is registered as general manager of MINDOR HOBBERSTAD HOLDING AS.

Where is MINDOR HOBBERSTAD HOLDING AS based?

MINDOR HOBBERSTAD HOLDING AS has its business address in Vikeså.

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.