BIZTRAC BETA
Wholesale of other machinery and equipment

SIVILINGENIØR STURE HEDLØV AS

Org. no. 935481945 Limited company (AS) Lier Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 4,000
Equity NOK 212,000
Incorporated 1984
Share capital NOK 2.0m

SIVILINGENIØR STURE HEDLØV AS is registered as a limited company in Lier, Buskerud with organisation number 935481945. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1984. Registered share capital is NOK 2.0m, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av verktøymaskiner med tilhørende utstyr, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 4,000
Equity
NOK 212,000
Est. value
NOK 132,000

Financial health · 2025

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

Who owns SIVILINGENIØR STURE HEDLØV AS?

HARALD HEDLØV
SIVILINGENIØR STURE HEDLØV AS
NOK 1.6m rev. · NOK 4,000 profit

SIVILINGENIØR STURE HEDLØV AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR STURE HEDLØV AS

Who owns SIVILINGENIØR STURE HEDLØV AS?

HARALD HEDLØV is the largest registered owner, with 90.0%.

What is the revenue of SIVILINGENIØR STURE HEDLØV AS?

SIVILINGENIØR STURE HEDLØV AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SIVILINGENIØR STURE HEDLØV AS?

Harald Hedløv is registered as general manager of SIVILINGENIØR STURE HEDLØV AS.

Where is SIVILINGENIØR STURE HEDLØV AS based?

SIVILINGENIØR STURE HEDLØV AS has its business address in Tranby.

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.