BIZTRAC BETA
Electrical installation

ELEKTRO FOSEN HOLDING AS

Org. no. 922898839 Limited company (AS) Ørland Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −25,000
Equity NOK 4.2m
Incorporated 2019
Share capital NOK 60,000

Signals

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

ELEKTRO FOSEN HOLDING AS is registered as a limited company in Ørland, Trøndelag with organisation number 922898839. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 200 shares. The company's stated purpose is: “Drive med investeringer av aksjer og eiendom, samt annen virksomhet som tilsvarer dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 4.2m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns ELEKTRO FOSEN HOLDING AS?

HOVD INVEST AS
ELEKTRO FOSEN HOLDING AS
NOK 0 rev. · NOK −25,000 profit

ELEKTRO FOSEN HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ELEKTRO FOSEN HOLDING AS own?

ELEKTRO FOSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ELEKTRO FOSEN HOLDING AS

Who owns ELEKTRO FOSEN HOLDING AS?

HOVD INVEST AS is the largest registered owner, with 40.0%.

What is the revenue of ELEKTRO FOSEN HOLDING AS?

ELEKTRO FOSEN HOLDING AS had revenue of NOK 0 in 2024.

Where is ELEKTRO FOSEN HOLDING AS based?

ELEKTRO FOSEN HOLDING AS has its business address in Brekstad.

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.