biztrac. BETA
COMPANY REGISTER PROFILE
954109674 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HELLEBRO AS

Org. no. 954109674 Limited company (AS) Ålesund Incorporated 1989 Active
Revenue 2025 NOK 1.4m
Operating profit NOK 1.0m
Equity NOK 1.7m
Incorporated 1989
Share capital NOK 4.0m

HELLEBRO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 954109674. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 4.0m, divided into 4049 shares. The company's stated purpose is: “Forvaltning av investeringsportefølje. Kjøp og salg av fast eiendom og selskaper, herunder deltakelse i andre selskaper med økonomisk vinst som formål. Videre kan selskapet selge alle typer datatjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 1.0m in operating profit.

Former names: HELLEBRO ENGROS & AGENTUR AS

Key figures · 2025

Revenue
NOK 1.4m
▲ +1083 %
Operating profit
NOK 1.0m
▲ +375 %
Equity
NOK 1.7m
▲ +90 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
18.2%
Very good
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns HELLEBRO AS?

HELLEBRO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELLEBRO AS

Who owns HELLEBRO AS?

Hans Christian Giske is the largest registered owner, with 44.6%.

What is the revenue of HELLEBRO AS?

HELLEBRO AS had revenue of NOK 1.4m in 2025.

Who is the general manager of HELLEBRO AS?

Hans Christian Giske is registered as general manager of HELLEBRO AS.

Where is HELLEBRO AS based?

HELLEBRO AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.