BIZTRAC BETA
Electrical installation

STRØM SERVICE AS

Org. no. 992908122 Limited company (AS) Gol Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 38.6m
Operating profit NOK 5.5m
Equity NOK 5.4m
Incorporated 2008
Employees 14
Share capital NOK 500,000

STRØM SERVICE AS is registered as a limited company in Gol, Buskerud with organisation number 992908122. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2008 and has 14 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Elektrisk installasjon og service, samt investering i fast eiendom. Selskapet kan delta i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.6m in revenue and NOK 5.5m in operating profit.

Key figures · 2024

Revenue
NOK 38.6m
Operating profit
NOK 5.5m
Equity
NOK 5.4m
Est. value
NOK 17.7m

Financial health · 2024

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

Who owns STRØM SERVICE AS?

HAUGSTAD INVEST AS
STRØM SERVICE AS
NOK 38.6m rev. · NOK 5.5m profit

STRØM SERVICE AS has 5 registered shareholders:

All shareholders and roles →

Which companies does STRØM SERVICE AS own?

STRØM SERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STRØM SERVICE AS

Who owns STRØM SERVICE AS?

HAUGSTAD INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of STRØM SERVICE AS?

STRØM SERVICE AS had revenue of NOK 38.6m in 2024.

Who is the general manager of STRØM SERVICE AS?

Ståle Haugstad is registered as general manager of STRØM SERVICE AS.

Where is STRØM SERVICE AS based?

STRØM SERVICE AS has its business address in Gol.

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.