BIZTRAC BETA
Electrical installation

AKTIV ELEKTRO AS

Org. no. 932830175 Limited company (AS) Sandefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 9.1m
Operating profit NOK 530,000
Equity NOK 440,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

AKTIV ELEKTRO AS is registered as a limited company in Sandefjord, Vestfold with organisation number 932830175. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Bygging og vedlikehold av andres elektriske anlegg og hva dermed står i forbindelse. Handel, investeringer i andre selskap og hva dermed står i forbindelse. Deltakelse i andre lignende selskaper. Kjøp og salg av varer og tjenester”. The most recent filed accounts, for the 2025 financial year, show NOK 9.1m in revenue and NOK 530,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.1m
Operating profit
NOK 530,000
Equity
NOK 440,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns AKTIV ELEKTRO AS?

BS ELEKTRO AS
AKTIV ELEKTRO AS
NOK 9.1m rev. · NOK 530,000 profit

AKTIV ELEKTRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKTIV ELEKTRO AS

Who owns AKTIV ELEKTRO AS?

BS ELEKTRO AS is the largest registered owner, with 51.0%.

What is the revenue of AKTIV ELEKTRO AS?

AKTIV ELEKTRO AS had revenue of NOK 9.1m in 2025.

Who is the general manager of AKTIV ELEKTRO AS?

Morten Veløy Haugan is registered as general manager of AKTIV ELEKTRO AS.

Where is AKTIV ELEKTRO AS based?

AKTIV ELEKTRO AS has its business address in Sandefjord.

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.