BIZTRAC BETA
Other technical consultancy

HANEBREKKE STÅL AS

Org. no. 999599176 Limited company (AS) Stad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 269,000
Equity NOK 1.1m
Incorporated 2012
Share capital NOK 30,000

HANEBREKKE STÅL AS is registered as a limited company in Stad, Vestland with organisation number 999599176. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Å utføre prosjektleiing, byggeleiing og andre konsulenttenester knytt til skipsbygging og annan industri, samt sal av dertil høyrande varer og tenester. Selskapet kan og delta i andre selskap med liknande verksemd.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 269,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 269,000
Equity
NOK 1.1m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns HANEBREKKE STÅL AS?

HERDIS MARIE ØYE HANEBREKKE
HANEBREKKE STÅL AS
NOK 4.2m rev. · NOK 269,000 profit

HANEBREKKE STÅL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANEBREKKE STÅL AS

Who owns HANEBREKKE STÅL AS?

HERDIS MARIE ØYE HANEBREKKE is the largest registered owner, with 50.0%.

What is the revenue of HANEBREKKE STÅL AS?

HANEBREKKE STÅL AS had revenue of NOK 4.2m in 2025.

Who is the general manager of HANEBREKKE STÅL AS?

Jonny Hanebrekke is registered as general manager of HANEBREKKE STÅL AS.

Where is HANEBREKKE STÅL AS based?

HANEBREKKE STÅL AS has its business address in Stårheim.

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.