biztrac. BETA
COMPANY REGISTER PROFILE
931119907 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

MJELDE BYGG HOLDING AS

Org. no. 931119907 Limited company (AS) Osterøy Incorporated 2023 Active
Operating profit NOK −117,000
Equity NOK 12.2m
Incorporated 2023
Share capital NOK 100,000

Signals

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

MJELDE BYGG HOLDING AS is registered as a limited company in Osterøy, Vestland with organisation number 931119907. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å eie og investere i aksjer, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −117,000
▼ −192 %
Equity
NOK 12.2m
▼ −0 %
Est. value
NOK 12.5m

Financial health · 2025

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

Who owns MJELDE BYGG HOLDING AS?

MJELDE BYGG HOLDING AS
· NOK −117,000 profit

MJELDE BYGG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MJELDE BYGG HOLDING AS own?

MJELDE BYGG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MJELDE BYGG HOLDING AS

Who owns MJELDE BYGG HOLDING AS?

BERGAN EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of MJELDE BYGG HOLDING AS?

Eirik Bergan is registered as general manager of MJELDE BYGG HOLDING AS.

Where is MJELDE BYGG HOLDING AS based?

MJELDE BYGG HOLDING AS has its business address in Lonevåg.

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.