BIZTRAC BETA
Construction of residential and non-residential buildings

BYGG HOLDCO AS

Org. no. 825979212 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −42,000
Equity NOK 96.9m
Incorporated 2020
Share capital NOK 1.0m

Signals

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

BYGG HOLDCO AS is registered as a limited company in Oslo, Oslo with organisation number 825979212. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 1.0m, divided into 500000 shares. The company's stated purpose is: “Eie selskaper, direkte eller indirekte, eller andeler av selskaper med virksomhet relatert til entreprenørvirksomhet, salg og konsulentvirksomhet samt hva hermed står i forbindelse. Selskapet kan videre eie og drive fast eiendom. Selskapet kan ved aksjeinnskudd, lån, garantistillelse eller på annen måte delta i annen næringsvirksomhet.”.

Key figures · 2025

Operating profit
NOK −42,000
Equity
NOK 96.9m
Est. value
NOK 106.2m

Financial health · 2025

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

Who owns BYGG HOLDCO AS?

KB GRUPPEN AS
BYGG HOLDCO AS
· NOK −42,000 profit

BYGG HOLDCO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BYGG HOLDCO AS own?

BYGG HOLDCO AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

BYGG HOLDCO AS er morselskap for 4 datterselskaper:

Frequently asked questions about BYGG HOLDCO AS

Who owns BYGG HOLDCO AS?

KB GRUPPEN AS is the largest registered owner, with 98.0%.

Where is BYGG HOLDCO AS based?

BYGG HOLDCO AS has its business address in Oslo.

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.