biztrac. BETA
COMPANY REGISTER PROFILE
934920333 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Electrical installation

B E ELEKTRO AS

Org. no. 934920333 Limited company (AS) Stavanger Incorporated 2025 Active
Revenue 2025 NOK 3.5m
Operating profit NOK 53,000
Equity NOK 23,000
Incorporated 2025
Employees 5
Share capital NOK 30,000

B E ELEKTRO AS is registered as a limited company in Stavanger, Rogaland with organisation number 934920333. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive elektrovirksomhet, generell elektroinstallasjon, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 53,000
Equity
NOK 23,000
Est. value
NOK 164,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
1.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns B E ELEKTRO AS?

B E ELEKTRO AS
NOK 3.5m rev. · NOK 53,000 profit

B E ELEKTRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about B E ELEKTRO AS

Who owns B E ELEKTRO AS?

STING CAPITAL AS is the largest registered owner, with 60.0%.

What is the revenue of B E ELEKTRO AS?

B E ELEKTRO AS had revenue of NOK 3.5m in 2025.

Who is the general manager of B E ELEKTRO AS?

Inger Egeland-Helgøy is registered as general manager of B E ELEKTRO AS.

Where is B E ELEKTRO AS based?

B E ELEKTRO AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.