BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGPROFFEN HOLDING AS

Org. no. 921885784 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −226,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 190,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−226k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-23 Adresseendring registrert 2026-02-23.

BYGGPROFFEN HOLDING AS is registered as a limited company in Bodø, Nordland with organisation number 921885784. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 190,000, divided into 11200 shares. The company's stated purpose is: “Holdingselskap. Investering i aksjer og øvrige verdipapirer.”.

Key figures · 2024

Operating profit
NOK −226,000
Equity
NOK 1.9m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
0.59
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.9%
Good
Equity as a share of total capital

Who owns BYGGPROFFEN HOLDING AS?

EIVIND NYHAGEN
BYGGPROFFEN HOLDING AS
· NOK −226,000 profit

BYGGPROFFEN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BYGGPROFFEN HOLDING AS own?

BYGGPROFFEN HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

BYGGPROFFEN HOLDING AS er morselskap for 3 datterselskaper:

Frequently asked questions about BYGGPROFFEN HOLDING AS

Who owns BYGGPROFFEN HOLDING AS?

EIVIND NYHAGEN is the largest registered owner, with 42.5%.

Where is BYGGPROFFEN HOLDING AS based?

BYGGPROFFEN HOLDING AS has its business address in Bodø.

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.