BIZTRAC BETA
Electrical installation

ELEKTRO EKSPERTEN AS

Org. no. 933547108 Limited company (AS) Osterøy Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 33,000
Equity NOK 51,000
Incorporated 2024
Share capital NOK 30,000

ELEKTRO EKSPERTEN AS is registered as a limited company in Osterøy, Vestland with organisation number 933547108. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen elektrikerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 33,000
Equity
NOK 51,000
Est. value
NOK 134,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.8%
Weak
Equity as a share of total capital

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

Who owns ELEKTRO EKSPERTEN AS?

PATRYK PONIEWAZ
ELEKTRO EKSPERTEN AS
NOK 2.7m rev. · NOK 33,000 profit

ELEKTRO EKSPERTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELEKTRO EKSPERTEN AS

Who owns ELEKTRO EKSPERTEN AS?

PATRYK PONIEWAZ is the largest registered owner, with 100.0%.

What is the revenue of ELEKTRO EKSPERTEN AS?

ELEKTRO EKSPERTEN AS had revenue of NOK 2.7m in 2025.

Who is the general manager of ELEKTRO EKSPERTEN AS?

Patryk Poniewaz is registered as general manager of ELEKTRO EKSPERTEN AS.

Where is ELEKTRO EKSPERTEN AS based?

ELEKTRO EKSPERTEN AS has its business address in Lonevåg.

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.