BIZTRAC BETA
Electrical installation

OLEKTRO AS

Org. no. 928524906 Limited company (AS) Namsos Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 40,000
Equity NOK 490,000
Incorporated 2021
Share capital NOK 200,000

OLEKTRO AS is registered as a limited company in Namsos, Trøndelag with organisation number 928524906. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Salg og montering av elektriske installasjoner, salg og montering av solcelleanlegg, salg, montering og vedlikehold av brannvarslingsanlegg og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 40,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 40,000
Equity
NOK 490,000
Est. value
NOK 313,000

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.1%
Good
Equity as a share of total capital

Who owns OLEKTRO AS?

GULJFESK INVEST AS
OLEKTRO AS
NOK 3.9m rev. · NOK 40,000 profit

OLEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLEKTRO AS

Who owns OLEKTRO AS?

GULJFESK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of OLEKTRO AS?

OLEKTRO AS had revenue of NOK 3.9m in 2025.

Who is the general manager of OLEKTRO AS?

Ole Marius Silset Brevik is registered as general manager of OLEKTRO AS.

Where is OLEKTRO AS based?

OLEKTRO AS has its business address in Namdalseid.

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.