BIZTRAC BETA
Construction of residential and non-residential buildings

METALL BYGG HOLDING AS

Org. no. 930894451 Limited company (AS) Steinkjer Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −73,000
Equity NOK 115.6m
Incorporated 2023
Share capital NOK 1.9m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−73k kr).

METALL BYGG HOLDING AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 930894451. 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 1.9m, divided into 926667 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, kan forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette. Selskapet kan også yte konserninterne tjenester.”.

Key figures · 2024

Operating profit
NOK −73,000
Equity
NOK 115.6m
Est. value
NOK 128.6m

Financial health · 2024

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

Who owns METALL BYGG HOLDING AS?

VELETA AS
METALL BYGG HOLDING AS
· NOK −73,000 profit

METALL BYGG HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does METALL BYGG HOLDING AS own?

METALL BYGG HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about METALL BYGG HOLDING AS

Who owns METALL BYGG HOLDING AS?

VELETA AS is the largest registered owner, with 32.3%.

Where is METALL BYGG HOLDING AS based?

METALL BYGG HOLDING AS has its business address in Steinkjer.

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.