BIZTRAC BETA
Electrical installation

BORCH FAGERHAUG ELEKTRO AS

Org. no. 911916975 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 159,000
Equity NOK 435,000
Incorporated 2013
Share capital NOK 30,000

BORCH FAGERHAUG ELEKTRO AS is registered as a limited company in Asker, Akershus with organisation number 911916975. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Elektrisk installasjonsvirksomhet, konsulentvirksomhet, kjøp og salg av elektrisk materiell herunder virksomhet som naturlig tilhører dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 159,000
Equity
NOK 435,000
Est. value
NOK 726,000

Financial health · 2025

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

Who owns BORCH FAGERHAUG ELEKTRO AS?

ØISTEIN BORCH
BORCH FAGERHAUG ELEKTRO AS
NOK 1.4m rev. · NOK 159,000 profit

BORCH FAGERHAUG ELEKTRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORCH FAGERHAUG ELEKTRO AS

Who owns BORCH FAGERHAUG ELEKTRO AS?

ØISTEIN BORCH is the largest registered owner, with 50.0%.

What is the revenue of BORCH FAGERHAUG ELEKTRO AS?

BORCH FAGERHAUG ELEKTRO AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BORCH FAGERHAUG ELEKTRO AS?

Øistein Borch is registered as general manager of BORCH FAGERHAUG ELEKTRO AS.

Where is BORCH FAGERHAUG ELEKTRO AS based?

BORCH FAGERHAUG ELEKTRO AS has its business address in Heggedal.

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.