BIZTRAC BETA
Electrical installation

H K SØRENSEN AS

Org. no. 945419849 Limited company (AS) Senja Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 23.3m
Operating profit NOK 1.3m
Equity NOK 3.2m
Incorporated 1987
Employees 14
Share capital NOK 100,000

H K SØRENSEN AS is registered as a limited company in Senja, Troms with organisation number 945419849. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 1987 and has 14 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Levere og montere elektriske installasjoner og hva derved står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 23.3m
Operating profit
NOK 1.3m
Equity
NOK 3.2m
Est. value
NOK 6.1m

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.5%
Very good
Equity as a share of total capital

Who owns H K SØRENSEN AS?

JAKOB INVEST 2 AS
H K SØRENSEN AS
NOK 23.3m rev. · NOK 1.3m profit

H K SØRENSEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does H K SØRENSEN AS own?

H K SØRENSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about H K SØRENSEN AS

Who owns H K SØRENSEN AS?

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

What is the revenue of H K SØRENSEN AS?

H K SØRENSEN AS had revenue of NOK 23.3m in 2025.

Who is the general manager of H K SØRENSEN AS?

Eivind Herold Jakobsen is registered as general manager of H K SØRENSEN AS.

Where is H K SØRENSEN AS based?

H K SØRENSEN AS has its business address in Finnsnes.

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.