BIZTRAC BETA
COMPANY REGISTER PROFILE
987189606 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Electrical installation

SOLHEIM ELEKTRO AS

Org. no. 987189606 Limited company (AS) Bjørnafjorden Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 93,000
Operating profit NOK −115,000
Equity NOK 1.7m
Incorporated 2004
Share capital NOK 100,000

Signals

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

SOLHEIM ELEKTRO AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 987189606. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Elektriske installasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 93,000 in revenue and NOK −115,000 in operating profit.

Key figures · 2025

Revenue
NOK 93,000
Operating profit
NOK −115,000
Equity
NOK 1.7m
Est. value
NOK 754,000

Financial health · 2025

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

Who owns SOLHEIM ELEKTRO AS?

HÅVARD SOLHEIM
SOLHEIM ELEKTRO AS
NOK 93,000 rev. · NOK −115,000 profit

SOLHEIM ELEKTRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLHEIM ELEKTRO AS

Who owns SOLHEIM ELEKTRO AS?

HÅVARD SOLHEIM is the largest registered owner, with 80.0%.

What is the revenue of SOLHEIM ELEKTRO AS?

SOLHEIM ELEKTRO AS had revenue of NOK 93,000 in 2025.

Who is the general manager of SOLHEIM ELEKTRO AS?

Håvard Solheim is registered as general manager of SOLHEIM ELEKTRO AS.

Where is SOLHEIM ELEKTRO AS based?

SOLHEIM ELEKTRO AS has its business address in Holmefjord.

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.