BIZTRAC BETA
Other technical consultancy

BILLKVAM & FAGERHAUG INSTALLASJON AS

Org. no. 919496622 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 149,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-03-20 Aksjekapital registrert 2026-03-20.

BILLKVAM & FAGERHAUG INSTALLASJON AS is registered as a limited company in Oslo, Oslo with organisation number 919496622. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 500000 shares. The company's stated purpose is: “Eie og forvalte aksjer i selskaper innenfor elektroentreprenørbransjen og tilstøtende bransjer, samt virksomhet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −13,000
Equity
NOK 149,000
Est. value
NOK 9.1m

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 BILLKVAM & FAGERHAUG INSTALLASJON AS?

HERBRANDSEN INVEST AS
BILLKVAM & FAGERHAUG INSTALLASJON AS
· NOK −13,000 profit

BILLKVAM & FAGERHAUG INSTALLASJON AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BILLKVAM & FAGERHAUG INSTALLASJON AS own?

BILLKVAM & FAGERHAUG INSTALLASJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BILLKVAM & FAGERHAUG INSTALLASJON AS

Who owns BILLKVAM & FAGERHAUG INSTALLASJON AS?

HERBRANDSEN INVEST AS is the largest registered owner, with 65.0%.

Where is BILLKVAM & FAGERHAUG INSTALLASJON AS based?

BILLKVAM & FAGERHAUG INSTALLASJON 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.